2.13.0

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