Bump com.launchdarkly:launchdarkly-android-client-sdk from 5.12.2 to 5.13.0 in /app

[dependabot]

Bumps com.launchdarkly:launchdarkly-android-client-sdk from 5.12.2 to 5.13.0.

Release notes

Sourced from com.launchdarkly:launchdarkly-android-client-sdk's releases.

v5.13.0

5.13.0 (2026-06-08)

Features

• experimental: Android Client SDK FDv2 EAP (#369) (2597ad8)

Data Saving Mode EAP

This release adds support for our second generation flag delivery protocol, also known as data-saving mode.

This SDK version uses the first generation flag delivery protocol unless you explicitly configure the new protocol.

Support for the new protocol is defined by a data system configuration. Setting a data system via Components.dataSystem() enables the new protocol.

The data system supports more flexible configuration for initializers (how the SDK gets an initial payload) and synchronizers (how it stays up to date).

This is an Early Access feature. The dataSystem configuration surface is subject to change without notice and is not covered by the SDK's semantic-versioning guarantees until it graduates to GA. Existing applications that do not call .dataSystem(...) are unaffected.

Configuration

Several predefined data system configurations are available depending on how you deploy the SDK. The Android Client SDK exposes the data system through the same ConnectionMode enum it already uses; the syntactic shape differs from the server SDKs because Android retains its existing foreground/background lifecycle semantics under FDv2. See Automatic mode switching below.

Default

This is the LaunchDarkly-recommended default. It uses a two-phase strategy for initialization and includes fallbacks for synchronization in each connection mode.

The SDK gets an initial payload with a single request to the polling endpoints, then keeps it up to date via streaming in the foreground. If that initial polling request fails, the SDK can still initialize via streaming once it enters synchronization. During synchronization the SDK can fall back to polling if streaming has problems. The SDK automatically switches to polling in the background and during network changes.

LDConfig config = new LDConfig.Builder(AutoEnvAttributes.Enabled)
    .mobileKey("my-key")
    .dataSystem(Components.dataSystem())
    .build();

Polling only or streaming only

You can configure the SDK to use only polling or only streaming in the foreground. This is not the recommended mode, and fewer fallbacks are available. To prevent the SDK from switching modes based on app lifecycle or network state, disable automatic mode switching:

Polling:

LDConfig config = new LDConfig.Builder(AutoEnvAttributes.Enabled)
    .mobileKey("my-key")
    .dataSystem(
        Components.dataSystem()
            .automaticModeSwitching(AutomaticModeSwitchingConfig.disabled())
            .foregroundConnectionMode(ConnectionMode.POLLING))
</tr></table> 

... (truncated)

Changelog

Sourced from com.launchdarkly:launchdarkly-android-client-sdk's changelog.

5.13.0 (2026-06-08)

Features

• experimental: Android Client SDK FDv2 EAP (#369) (2597ad8)

Commits

• b10dd6d chore(main): release 5.13.0 (#370)
• 2597ad8 feat(experimental): Android Client SDK FDv2 EAP (#369)
• 9f47e98 Update SECURITY.md to reflect bug bounty program (#366)
• 5574cec Update SECURITY.md to reflect bug bounty program
• 1c1549e test: make callbackNotFiredBeforeDebounceWindow deterministic (#364)
• fab29d5 test: make callbackNotFiredBeforeDebounceWindow deterministic
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.