Skip to content

Releases: launchdarkly/ios-client-sdk

2.9.0

05 Dec 05:26
dde751a

Choose a tag to compare

[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

13 Oct 21:20

Choose a tag to compare

[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

26 Sep 18:46

Choose a tag to compare

[2.7.0] - 2017-09-25

Changed

  • Updated to support Xcode 9 and iOS 11

2.6.1

26 Sep 18:44

Choose a tag to compare

[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

26 Aug 00:55

Choose a tag to compare

[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

03 Aug 22:38

Choose a tag to compare

[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

09 Jul 07:48

Choose a tag to compare

[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

21 Jun 05:50

Choose a tag to compare

[2.4.2] - 2017-06-20

Fixed

  • Race condition in LDPollingManager identified by Thread Sanitizer

2.4.1

15 Jun 22:07

Choose a tag to compare

[2.4.1] - 2017-06-15

Fixed

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

2.4.0

13 Jun 17:52

Choose a tag to compare

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