Releases: launchdarkly/android-client-sdk
Releases · launchdarkly/android-client-sdk
2.1.1
[2.1.1] - 2017-11-27
Fixed
AndroidManifest.xmlno longer enforcessupportsRtl="true"- Client no longer reconnects after detecting an invalidated mobile key
- Client can be initialized outside the main thread. Thanks @jonathanmgrimm!
2.1.0
[2.1.0] - 2017-10-13
Added
LDConfig.Builder#setUseReportmethod to allow switching the request verb fromGETtoREPORT. Do not use unless advised by LaunchDarkly.
Changed
LDClient.initvalidates that its arguments are non-null.
Fixed
- Stream connections are closed completely when the app enters background mode.
- Fewer HTTP requests are made to the LaunchDarkly service when feature flags are updated frequently.
- Potential
NullPointerExceptionin thevariationmethods. - Removed spurious error when
LDClientis initialized while the device is offline.
2.0.5
2.0.4
[2.0.4] - 2017-05-26
Changed
- Modified default and minimum background polling intervals.
- Improved http client lifecycle management.
- Improved offline saving of flags when switching users.
2.0.3
[2.0.3] - 2017-05-18
Changed
Even better thread safety in UserManager when removing change listeners.
2.0.2
[2.0.2] - 2017-05-03
Changed
- Improved thread safety in UserManager when removing change listeners.
- Streamlined SDK initialization.
2.0.1
2.0.0
[2.0.0] - 2017-04-10
Added
- More configurable flag update mechanisms including the ability to disable streaming. See README.md for details.
Changed
- API BREAKING CHANGE: Guava ListenableFuture is no longer returned from LDClient. Instead we're returning java.util.concurrent.Future.
- Added configurable background polling.
- Improved Json variation handling.
- Improved stream connection lifecycle management.
- Removed SLF4J logger in LDUser.
- Updated suggested Proguard rules for a smaller footprint.
Fixed
1.0.1
1.0.0
Please see full documentation here: http://docs.launchdarkly.com/v2.0/docs/android-sdk-reference