Skip to content
Compare
Choose a tag to compare

[1.2.0] - 2021-07-23

Added:

  • Added the Alias method. This can be used to associate two user objects for analytics purposes with an alias event.

Fixed:

  • DoubleVariation is now guaranteed to return a Double value rather than an integer or Float type, regardless of whether the value could be represented as an integer.
Compare
Choose a tag to compare

[1.1.5] - 2020-05-19

Changed:

  • Refactored internal event processing logic
Compare
Choose a tag to compare

[1.1.4] - 2020-05-13

Fixed:

  • Corrected summary event schema to no longer include user info
Compare
Choose a tag to compare

[1.1.3] - 2020-04-10

Fixed:

  • Standardized streaming retry behavior. First delay is always 1 second, delay is capped at 30 seconds, and if the stream is productive for 60 seconds reset back-off.
Compare
Choose a tag to compare

[1.1.2] - 2020-01-27

Fixed:

  • The SDK will no longer send empty event payloads to LaunchDarkly.
cbbcff3
Compare
Choose a tag to compare

[1.1.1] - 2020-01-17

Fixed

  • The SDK now specifies a uniquely identifiable request header when sending events to LaunchDarkly to ensure that events are only processed once, even if the SDK sends them two times due to a failed initial attempt.
  • The SDK will now retry event delivery on failure.
667bc5d
Compare
Choose a tag to compare

[1.1.0] - 2019-11-12

Added

  • A LaunchDarklySDKVersion function that returns the SDK version
2676fd8
Compare
Choose a tag to compare

[1.0.1] - 2019-11-08

Fixed

  • Dereference of an invalid value in streaming mode
84f1c1e
Compare
Choose a tag to compare

[1.0.0] - 2019-11-04

First GA release. No associated changes.

0a2873f
Compare
Choose a tag to compare

1.0.0-rc.3

Pre-release
Pre-release

[1.0.0-rc.3] - 2019-10-24

Added

  • Added support for the new LaunchDarkly experimentation functionality. An optional numeric metric parameter has been added the track method.
  • The new family of *VariationDetail methods allows you to evaluate a feature flag (using the same parameters as you would for *Variation) and receive more information about how the value was calculated. This information is returned in an object that contains both the result value and a "reason" object which will tell you, for instance, if the user was individually targeted for the flag or was matched by one of the flag's rules, or if the flag returned the default value due to an error.