Skip to content

Commit 88fbb57

Browse files
author
LaunchDarklyReleaseBot
committed
Releasing version 3.2.0
1 parent 51de904 commit 88fbb57

File tree

2 files changed

+13
-1
lines changed

2 files changed

+13
-1
lines changed

CHANGELOG.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,18 @@
33

44
All notable changes to the LaunchDarkly Android SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
55

6+
## [3.2.0] - 2022-08-23
7+
The purpose of this release is to introduce a new logging facade, [`com.launchdarkly.logging`](https://github.com/launchdarkly/java-logging), to streamline how logging works in LaunchDarkly Java and Android code.
8+
9+
Previously, the Android SDK always used Timber for logging. This sometimes led to conflicts with an application's separate use of Timber, as described in [#88](https://github.com/launchdarkly/android-client-sdk/issues/88) and [#147](https://github.com/launchdarkly/android-client-sdk/issues/147).
10+
11+
In this release, the default behavior is still to use Timber, but the logging facade can also be configured programmatically to do simple Android logging without Timber, or to forward output to another framework such as `java.util.logging`, or to multiple destinations, or to capture output in memory. In a future major version release, the default behavior may be changed so that the SDK does not require Timber as a dependency.
12+
13+
### Added:
14+
- In [`LDConfig.Builder`](https://javadoc.io/doc/com.launchdarkly/launchdarkly-android-client-sdk/latest/com/launchdarkly/sdk/android/LDConfig.Builder.html), the new methods `logAdapter`, `logLevel`, and `loggerName`, for the new logging capabilities mentioned above.
15+
- New class `LDTimberLogging` for configuring the SDK's Timber integration.
16+
- New class `LDAndroidLogging` for configuring the SDK to use the Android logging API without Timber.
17+
618
## [3.1.8] - 2022-08-23
719
### Changed:
820
- Changed throttling/jitter logic that used `java.util.Random` to use `java.security.SecureRandom`. Even though in this case it is not being used for any cryptographic purpose, but only to produce a pseudo-random delay, static analysis tools may still report every use of `java.util.Random` as a security risk by default. The purpose of this change is simply to avoid such warnings; it has no practical effect on the behavior of the SDK.

gradle.properties

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616
# This option should only be used with decoupled projects. More details, visit
1717
# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
1818
# org.gradle.parallel=true
19-
version=3.1.8
19+
version=3.2.0
2020

2121
sonatypeUsername=
2222
sonatypePassword=

0 commit comments

Comments
 (0)