AdMob's Android SDK v25 is the end of the legacy line — sunset dates mean no-fill risk, and the next step is the Next-Gen SDK
This is a fill problem, not a payout problem. Nothing here touches identity checks or payment holds. It is about which version of the Android SDK your users are still running, and what Google does with ad requests from old versions.
Google says the Google Mobile Ads SDK (Legacy) for Android is in maintenance mode, and its deprecation table now ends the legacy line at v25. The v25 migration path is "Migrate to GMA Next-Gen SDK", and v24 and v25 share the same deprecation date (30 June 2027) and sunset date (30 June 2028). Moving to the newest legacy version therefore buys time, not a future. Sunset is a revenue event, not a warning: traffic from a sunset version "is at risk of receiving automatic no fill". v22 has been in that state since 30 June 2026, and v23 joins on 30 June 2027.
What the legacy Android page says now
The Android deprecation and release-notes pages for the legacy SDK carry the banner “Google Mobile Ads SDK is in maintenance mode. For the latest updates and features, migrate and set up GMA Next-Gen SDK.” The timetable on the deprecation page (last updated 2026-11-09 UTC) reads:
- v25.x.x — Supported · released February 17, 2026 · deprecation June 30, 2027 · sunset June 30, 2028 · migration guide: “Migrate to GMA Next-Gen SDK”
- v24.x.x — Supported · released February 24, 2025 · deprecation June 30, 2027 · sunset June 30, 2028 · “Migrate to v25”
- v23.x.x — Deprecated · deprecation February 17, 2026 · sunset June 30, 2027 · “Migrate to v24”
- v22.x.x — Sunset · sunset June 30, 2026 · “Migrate to v23”
- v21 and older — Sunset
The table is the source. Google has not posted a sentence saying there will never be a v26. What the table shows is that the v25 row points to Next-Gen rather than to another legacy version.
What “sunset” means, in Google’s words
“After an SDK version is sunset, ad traffic from that version is at risk of receiving automatic no fill due to stopped ad serving.” The status table explains how that risk becomes real: for sunset versions Google says “We will regularly review usage of all sunset versions going forward to consider disabling ad serving. The oldest versions with lower usage and higher maintenance costs will be targeted first. When ad serving is disabled, ad requests return a no fill with an error indicating that this version is sunset.” So a sunset date is not a promise that ads stop that morning. It is the date from which Google may disable ad serving for that version. Deprecated versions still serve ads but lose technical support. Google also keeps the right to move early: the schedule “does not preclude us from sunsetting an SDK version at an earlier date.”
Mediation: check the compatibility list first
Google’s Next-Gen migration page says that if you reach AdMob through a third-party mediation platform that supports partner bidding, you should check its table. As fetched on 2026-11-10, the platforms listed as compatible with GMA Next-Gen SDK are: AdMost, AppLovin MAX, Chartboost Mediation, DT Fairbid, Gravite, Nimbus, TopOn, TradPlus VisiM, Unity LevelPlay. For anything not on the list, Google’s instruction is: “contact your mediation platform to request support.” The list is Google’s, it is not a ranking, and it can change. Re-read it on the day you plan the move.
The adapter trap
The same page says: “Mediation adapters continue to depend on Google Mobile Ads SDK (Legacy). However, GMA Next-Gen SDK includes all classes required by mediation adapters.” To avoid duplicate-symbol compile errors, Google says to “exclude both play-services-ads and play-services-ads-lite modules globally from all dependencies” in the app-level build file. The Next-Gen artifact itself is com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk (the page’s example uses 1.6.0). The page also lists a minimum Android API level of 24 and a compile API level of 34, and says Next-Gen “requires initialization before loading ads”. Copy the exact Gradle blocks from Google’s migration page, not from this article.
Next-Gen has its own clock
The Next-Gen deprecation page lists v1.x.x as released April 14, 2026, with deprecation Q1 2028 and sunset Q2 2029. v0.x.x-beta: deprecation Q1 2027, sunset Q2 2028. v0.x.x-alpha: already deprecated, sunset June 30, 2027. For quarter-only dates, Google says “A more specific sunset date will be announced on the Google Ads Developer blog, and updated on this page with two months notice.” Use these official dates, not launch dates reported elsewhere.
One callback note for rewarded ads
The Next-Gen 1.6.0 release notes (2026-10-22) say Google “Fixed a bug in rewarded and rewarded interstitial ads where the OnUserEarnedRewardListener.onUserEarnedReward() method could be invoked after the AdEventCallback.onAdDismissedFullScreenContent() method.” If your reward logic assumes the reward arrives before the dismiss callback, do not rely on the order. Make reward granting idempotent so each ad view grants once, whichever callback fires first.
iOS is a different table
Do not copy the Android dates to iOS. The iOS deprecation page lists v13 and v12 as supported (v12 deprecation Q1 2027), v11 as deprecated with sunset Q2 2027, and v10 with sunset June 30, 2026. Check the iOS page for iOS builds.
Inventory checklist (Android)
- For every live Android build that still has real users, including old builds, note the major version of
play-services-ads. - v22 or lower: that traffic is already sunset and at risk of automatic no fill.
- v23: sunset is June 30, 2027. Upgrade before then.
- v24 or v25: both deprecate June 30, 2027 and sunset June 30, 2028. Moving from v24 to v25 buys no extra sunset time. Plan Next-Gen.
- If you use third-party mediation, confirm your platform is on Google’s live compatibility list before you plan Next-Gen, then apply the
play-services-ads/play-services-ads-liteexclusion. - Rewarded formats: make reward granting idempotent (see 1.6.0).
What this article is not
Not a payout or verification issue, and not a regulatory queue. TCF problems sit in a separate place (regulatory queue ≠ SDK lifecycle). SDK lifecycle ≠ network policy.
Not legal advice. Wording is quoted or paraphrased from Google’s public AdMob developer pages as fetched on 2026-11-10. Dates can move; re-check the official tables before you plan a release.
Sources
- Deprecation and sunset — Google Mobile Ads SDK (Legacy) for Android (https://developers.google.com/admob/android/deprecation)
- GMA Next-Gen SDK — Deprecation and sunset (https://developers.google.com/admob/android/next-gen/deprecation)
- GMA Next-Gen SDK — Migration (https://developers.google.com/admob/android/next-gen/migration)
- GMA Next-Gen SDK — Release notes (https://developers.google.com/admob/android/next-gen/rel-notes)
- Google Mobile Ads SDK (Legacy) for Android — Release notes (https://developers.google.com/admob/android/rel-notes)
- Deprecation and sunset — iOS (https://developers.google.com/admob/ios/deprecation)