Skip to content

Releases: launchdarkly/ios-client-sdk

2.13.7

16 Oct 05:38
1159f5e
Compare
Choose a tag to compare

[2.13.7] - 2018-10-15

Changed

  • Initializing LDClient in polling mode no longer blocks the calling thread.

2.13.6

06 Oct 00:51
Compare
Choose a tag to compare

[2.13.6] - 2018-10-05

Fixed

  • LDClient's updateUser did not attempt to retrieve the new user's cached flag values.
  • Fixed defect preventing a user's feature flags from being cached correctly under certain conditions.

2.13.5

24 Sep 03:41
Compare
Choose a tag to compare

[2.13.5] - 2018-09-23

Changed

  • Repairs Carthage build errors caused by higher fidelity checks in Xcode 10's new build engine.
  • Removes CLANG_WARN_DEPRECATED_OBJC_IMPLEMENTATIONS from the podspec, allowing Xcode 10's default setting to be used

2.13.4

23 Aug 22:06
Compare
Choose a tag to compare

[2.13.4] - 2018-08-23

Changed

  • Update to DarklyEventSource 3.2.7

2.13.3

15 Aug 18:47
6d128c9
Compare
Choose a tag to compare

[2.13.3] - 2018-08-15

Changed

  • Synchronized summary event creation to limit thread access and protect data integrity
  • Improved the robustness of the code creating summary events to better handle unexpected data

2.13.2

28 Jul 04:46
0f872b3
Compare
Choose a tag to compare

[2.13.2] - 2018-07-27

Fixed

  • Updated DarklyEventSource in order to fix potential flag stream parsing issues.

2.13.1

26 Jun 00:55
Compare
Choose a tag to compare

[2.13.1] - 2018-06-25

Changed

  • Removed early tests for reaching event capacity that caused benign Thread Sanitizer warnings
  • Changed pointer nil tests to clear Static Analyzer pointer comparison warnings

2.13.0

01 Jun 23:40
Compare
Choose a tag to compare

[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

24 Apr 17:19
b2de9bb
Compare
Choose a tag to compare

[2.12.1] - 2018-04-24

Changed

  • Clears selected warnings in CocoaPods project

2.12.0

23 Apr 04:16
55e0f4e
Compare
Choose a tag to compare

[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.