You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 method setInlineUsersInEvents in LDConfig. When true includes the full user (excluding private attributes) in analytics feature and custom events. When false includes only the userKey. Default: false.
The minimum polling interval is now 5 minutes, and the default event publishing interval is 30 seconds.
HTTP requests are cached in the app's cache directory.
The SDK now provides a consumer-proguard-rules.pro file containing recommended ProGuard rules.
Due to a Guava dependency update, we recommend a new ProGuard rule which you may need to add if the rules in consumer-proguard-rules.pro are not applied automatically:
Support for specifying private user attributes in order to prevent user attributes from being sent in analytics events back to LaunchDarkly. See the allAttributesPrivate and setPrivateAttributeNames methods on LDConfig.Builder as well as the privateX methods on LDUser.Builder.