AdMob 24.1’s Kotlin floor can block an otherwise ready launch
Analysis
By UA Ledger staff — 2 min read

Dependency compatibility should be verified in the build environment that produces the release.
An SDK upgrade can become a launch dependency through the build toolchain, even when the game’s ad placements are unchanged. The AdMob 24.1 Kotlin requirement is a concrete example worth preserving in an inherited project’s compatibility record.
Check the environment that produces the artifact
Our recommendation is to capture the resolved Kotlin version and the dependency version from the release build. A developer’s working local environment is helpful, but it is not the same evidence as a successful build in the service that produces the submitted artifact.
If a publisher receives binaries from an external studio, ask for the build record rather than a broad assurance that dependencies are current. The purpose is to make a failure reproducible and assignable. It is not to require every growth operator to understand the implementation details.
Protect the release dependency in the media plan
Where new creative depends on a game update, track the build as a prerequisite with an owner and a fallback date. Where the live game already supports the campaign promise, determine whether the SDK upgrade is actually on its critical path.
The provided card records a historical compatibility change. It does not claim a current studio build is broken or recommend a toolchain version independently of the full project. The next check is a concrete release artifact and its build evidence, followed by the usual integration and player-experience verification.
The governing record is Android release notes — 24.1.0. This edition checks the provider documentation; it does not inspect a studio account or certify a shipped build.
Inspect the evidence
Download the applicability and deadline record. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Provider | |
| Effective or release date | 2025-03-12 |
| Applies to | Android builds adopting Google Mobile Ads SDK 24.1.0 |
| Documented change | Version 24.1.0 specifies Kotlin 2.1.0 as its minimum Kotlin version. |
| Suggested owner | Android build engineering |
| Next verification | Run the release build with the resolved toolchain and dependency versions. |
Further reading in the existing archive: The MMP Migration Checklist to Run Before You Switch; LiveOps events as acquisition moments. These links provide background; this check does not independently verify their full contents.
Featured
Related posts
measurement
platforms
·1 min read
When to turn rewarded ads off for payers (and how to measure the loss)
measurement
platforms
·1 min read
When custom product pages need their own MMP campaign mapping
measurement
platforms
·1 min read
Season pass refund rate versus standard IAP refund rate
measurement
platforms
·1 min read
Pre-reg cohort quality vs post-launch paid cohort quality
More from the Measurement desk
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
measurement
platforms
·1 min read
Pity-adjusted expected value versus player-facing banner claims
measurement
platforms
·1 min read