iOS SDK

[2.13.0] - 2018-06-01

Added

• To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option inlineUsersInEvents. For more details, see Analytics Data Stream Reference.
• New property inlineUserInEvents in LDConfig. When YES includes the full user (excluding private attributes) in analytics feature and custom events. When NO includes only the userKey. Default: NO.
• Calling start or updateUser (when started) on LDClient logs an analytics identify event. identify events contain the full user (excluding private attributes) regardless of inlineUserInEvents.
• Adds analytics summary event used to track feature flag requests to the SDK.
• Adds analytics debug event available to assist with debugging when requested from the new Debugger in the LaunchDarkly UI.

Fixed

• Under some conditions, the SDK would not update flag values initially after connecting to the LaunchDarkly service.
• The SDK was reporting incorrect dates in analytics events sent from watchOS.

[2.12.1] - 2018-04-24

Changed

• Clears selected warnings in CocoaPods project

[2.12.0] - 2018-04-22

Added

• LDClient isOnline readonly property that reports the online/offline status.
• LDClient setOnline method to set the online/offline status. setOnline may operate asynchronously, so the client calls an optional completion block when the requested operation completes.

Changed

• Fixed potential memory leak with DarklyEventSource.

Removed

• LDClient online and offline methods.

Fixed

• Calling updateUser on LDClient while streaming no longer causes the SDK to request feature flags. The SDK now disconnects from the LaunchDarkly service and reconnects with the updated user.
• Calling updateUser on LDClient while polling now resets the polling timer after making a feature flag request.

[2.11.1] - 2018-03-26

Changed

• Changes the minimum required DarklyEventSource to version 3.2.0 in the CocoaPods podspec

[2.11.0] - 2018-03-15

Added

• Support for enhanced feature streams, facilitating reduced SDK initialization times.

Changed

• The streamUrl property on LDConfig now expects a path-less base URI.

[2.10.1] - 2018-02-15

Changed

• The minimum polling interval is now 5 minutes.

Fixed

• Removes user flag config values from event reports
• Improves SSE connection error handling

[2.10.0] - 2018-02-01

Added

• Support for specifying private user attributes in order to prevent user attributes from being sent in analytics events back to LaunchDarkly. See the allUserAttributesPrivate and privateUserAttributes properties of LDConfig as well as the privateAttributes property of LDUserBuilder.

[2.9.1] - 2017-12-05

Fixed

• Carthage builds no longer crash due to a missing DarklyEventSource library.

[2.9.0] - 2017-11-29

Changed

• LDClientManager no longer extends UIApplicationDelegate. The framework is now marked as extension-safe. Thanks @atlassian-gaustin!

Added

• Detect 401 Unauthorized response on flag & event requests, and take the client offline when detected.
• Detect LDEventSource report of 401 Unauthorized response on connection requests, and take the client offline when detected.
• LDClient delegate method userUnchanged called when the client receives a feature flag update that does not change any flag keys or values. Thanks @atlassian-gaustin!
• Xcode 9 support

Fixed

• LDPollingManager now reads the config set at the time of the startPolling message and configures polling timers accordingly.
• LDRequestManager now reads the config set at the time of the performRequest message to configure the API request.
• Removes duplicate LDEventSource libraries linked warning
• updateUser now updates the LDUser anonymous property when using a default user key.

[2.8.0] - 2017-10-13

Added

• useReport property on LDConfig to allow switching the request verb from GET to REPORT. Do not use unless advised by LaunchDarkly.

[2.7.0] - 2017-09-25

Changed

• Updated to support Xcode 9 and iOS 11

[2.6.1] - 2017-09-21

Added

-streamUrl property on LDConfig to allow customizing the Server Sent Events engine in streaming mode.

[2.6.0] - 2017-08-25

Added

• doubleVariation method for double value feature flags, as an alternative to numberVariation. Thanks @atlassian-gaustin!
• serverConnectionUnavailable ClientDelegate method called when the LDClient receives an error response to a feature flag request. Thanks @atlassian-gaustin!

Changed

• Prevent creating an EventSource when an EventSource is already running. Thanks @atlassian-gaustin!
• Move feature flag response processing to the request thread, and once complete return the result on the main thread. Thanks @atlassian-gaustin!

Fixed

• Array and Dictionary flags now return the array or dictionary when available from the server instead of always returning fallback values. Thanks @atlassian-gaustin!
• Streaming no longer generates multiple feature flag requests on return to the foreground

[2.5.1] - 2017-08-03

Fixed

• Feature flag requests for users with non-ASCII data are now encoded correctly
• UserUpdatedNotification posts only when the feature flag configuration changes for the user
• Events are no longer added to the event store when capacity is reached
• Resolve potential symbol conflicts with EventSource
• Feature flag request payloads are much smaller

[2.5.0] - 2017-07-09

Added

• The name property in LDUserBuilder, for setting a full name. This property complements the existing firstName and lastName properties.

Changed

• LDConfig has been refactored to replace the Builder pattern expected with LDConfigBuilder. Thanks @petrucci34!

Deprecated

• LDConfigBuilder has been deprecated and will be removed in the 3.0 release.
• The withXXX methods of LDUserBuilder have been deprecated in favor of properties. These methods will be removed in the 3.0 release.

[2.4.2] - 2017-06-20

Fixed

• Race condition in LDPollingManager identified by Thread Sanitizer

[2.4.1] - 2017-06-15

Fixed

• Memory leak with NSURLSession in EventSource. Thanks @jimmaye!

Added

• The client's background fetch interval can be configured using withBackgroundFetchInterval.

Changed

• By default, the client allows one background fetch per 60 minutes.

Fixed

• Memory leak with NSURLSession in LDRequestManager. Thanks @jimmaye!
• Race condition when the client is used in multiple threads

[2.3.3] - 2017-05-25

Changed

• Feature flag persistence is now more efficient

Fixed

• Client crashes if a feature flag is off and no off-variation is specified

[2.3.2] - 2017-05-18

Changed

• The default connection timeout is now actually 10 seconds, down from the system default of 60 seconds. Use withConnectionTimeout to change the setting.

Fixed

• Potential race conditions when HTTP requests exceed 10 seconds
• HTTP requests now honor the configured connection timeout