Skip to content

Releases: launchdarkly/android-client-sdk

v5.1.0

14 Mar 20:47
28e5977
Compare
Choose a tag to compare

5.1.0 (2024-03-14)

Features

  • Always inline contexts for feature events (2a88ef6)
  • Redact anonymous attributes within feature events (2a88ef6)

Bug Fixes

  • Bump launchdarklyJavaSdkInternal to 1.3.0 (#257) (2a88ef6)

v5.0.5

07 Mar 17:51
c009623
Compare
Choose a tag to compare

5.0.5 (2024-03-07)

Bug Fixes

  • propagating NPE fix for ContextBuilder.fromContext bug (#246) (3205005)

4.3.1

29 Feb 17:47
Compare
Choose a tag to compare

[4.3.1] - 2024-02-29

Fixed:

  • Improved thread usage in streaming connections.

5.0.4

27 Feb 20:16
Compare
Choose a tag to compare

[5.0.4] - 2024-02-27

Fixed:

  • Improved thread usage in streaming connections.

5.0.3

02 Feb 15:33
Compare
Choose a tag to compare

[5.0.3] - 2024-02-02

Fixed:

  • Fixes a rare bug (one occurrence) in which a race condition between identify and network state change could result in a crash.

5.0.2

19 Sep 19:03
Compare
Choose a tag to compare

[5.0.2] - 2023-09-19

Fixed:

  • Fixed a rare bug in key generation in some contexts generated by the Auto Environment Attributes feature.

5.0.1

25 Aug 17:54
Compare
Choose a tag to compare

[5.0.1] - 2023-08-25

Fixed:

  • Updated how Auto Environment Attributes sanitizes and validates provided values to provide a more user friendly experience.

5.0.0

03 Aug 21:29
Compare
Choose a tag to compare

[5.0.0] - 2023-08-03

Added:

  • Added Automatic Mobile Environment Attributes functionality which makes it simpler to target your mobile customers based on application name or version, or on device characteristics including manufacturer, model, operating system, locale, and so on. To learn more, read Automatic environment attributes.

Removed

4.3.0

03 Aug 19:03
Compare
Choose a tag to compare

[4.3.0] - 2023-08-03

Changed:

4.2.3

07 Jun 14:27
Compare
Choose a tag to compare

[4.2.3] - 2023-06-07

Fixed:

  • Streaming data connection to a relax proxy now calls the callback correctly after fetching the flag data.
  • Flag listeners are now called correctly after identify results in flag value changes.