Skip to content

Update LaunchDarkly Android Client SDK to 5.11.0#5

Open
devin-ai-integration[bot] wants to merge 2 commits intomainfrom
devin/1772498438-update-android-sdk
Open

Update LaunchDarkly Android Client SDK to 5.11.0#5
devin-ai-integration[bot] wants to merge 2 commits intomainfrom
devin/1772498438-update-android-sdk

Conversation

@devin-ai-integration
Copy link

@devin-ai-integration devin-ai-integration bot commented Mar 3, 2026

Summary

Bumps launchdarkly-android-client-sdk from 4.2.2 to 5.11.0 — a major version upgrade (4.x → 5.x).

SDK 5.11.0 requires newer build tooling than what the project previously used (AGP 4.1.3 / Gradle 6.7). The build configuration has been modernized to match.

Updates since last revision

Upgraded the entire build toolchain for SDK 5.11.0 compatibility:

Component Before After
AGP 4.1.3 8.7.0
Gradle wrapper 6.7 8.9
compileSdk / targetSdk 33 34
minSdk 21 24

Additional structural changes:

  • Migrated build.gradle from legacy buildscript/allprojects DSL to modern plugins DSL
  • Added pluginManagement and dependencyResolutionManagement blocks to settings.gradle
  • Moved namespace from AndroidManifest.xml package attribute to app/build.gradle (required by AGP 8.x)

Review & Testing Checklist for Human

  • Verify minSdk 24 is actually required. This was bumped from 21 — confirm whether SDK 5.x truly requires API 24+. If not, revert to 21 to avoid dropping Android 5.0–6.x device support unnecessarily.
  • Verify API compatibility across the v4 → v5 boundary. The app code uses LDClient, LDConfig.Builder, LDContext, ContextKind, and LaunchDarklyException. Confirm none of these were removed or had breaking signature changes in v5. Check the SDK changelog / migration guide for breaking changes.
  • Build the project in Android Studio and confirm it compiles without errors. The build.gradle and settings.gradle were substantially rewritten (legacy → modern DSL migration), so verify Gradle sync and build succeed.
  • Run the app on an emulator or device with a valid mobile key and confirm flag evaluation works end-to-end.
  • Check that LaunchDarklyException (used in MainActivity.java catch block) still exists and is thrown in the same circumstances in v5.

Notes

  • No CI exists on this repo — there is zero automated build validation. All verification must be done manually.
  • This change was not tested locally — no Android build toolchain was available in the build environment. Human verification is required.
  • This is a major version bump plus a significant build tooling overhaul; CI alone would be insufficient even if it existed.
  • Requested by: rlamb@launchdarkly.com
  • Devin Session

Updates the launchdarkly-android-client-sdk dependency from 4.2.2
to 5.11.0, the latest release of the LaunchDarkly Android Client SDK.

Co-Authored-By: rlamb@launchdarkly.com <rlamb@launchdarkly.com>
@devin-ai-integration
Copy link
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@kinyoklion kinyoklion marked this pull request as ready for review March 3, 2026 21:03
@kinyoklion kinyoklion requested a review from a team as a code owner March 3, 2026 21:03
SDK 5.11.0 requires newer build tooling. Updates:
- AGP: 4.1.3 → 8.7.0 (migrated from buildscript to plugins DSL)
- Gradle wrapper: 6.7 → 8.9
- compileSdk/targetSdk: 33 → 34
- minSdk: 21 → 24
- Added pluginManagement and dependencyResolutionManagement to settings.gradle
- Moved namespace from AndroidManifest.xml to build.gradle (AGP 8.x requirement)

Co-Authored-By: rlamb@launchdarkly.com <rlamb@launchdarkly.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant