BestPaid guides · Mobile apps · Google AdMob

AdMob SDK sunset: Android 22.x, iOS 10.x and Unity plugin 8.x have been at risk of no fill since June 30, 2026. How to upgrade without losing revenue

On June 30, 2026 Google sunset Google Mobile Ads SDK 22.x for Android and 10.x for iOS, plus the Unity and Flutter plugin versions built on them; more follow in 2027. Here is how to find the users still on old SDKs and upgrade each platform and its mediation adapters without losing revenue.

Sources: Google's AdMob deprecation pages for Android (Legacy), Next-Gen, iOS, Unity and Flutter (all last updated November 18, 2026); Google Advertising and Measurement Developer Blog (formerly Google Ads Developer Blog) posts on Android 25.0.0, iOS 13.0.0, Next-Gen as the preferred Android SDK, CocoaPods read-only mode and iOS adapters on Swift Package Manager; migration guides for Android (Legacy), Next-Gen and iOS; the iOS quick start; release notes for Android, Next-Gen and iOS; the Unity plugin changelog, quick start and Next-Gen guide; the google_mobile_ads changelog and Next-Gen guide; the React Native quick start; Other platforms; the Ads Activity report help; AdMob API report dimensions and networkReport.generate; API references for Android, iOS, Flutter and Unity; mediation networks; the AppLovin Android adapter changelog; Android in-app updates; Google Play staged rollouts; App Store Connect phased releases. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What was sunset on June 30, 2026

SDKSunset June 30, 2026Next to sunsetSupported
Android: Google Mobile Ads SDK, now called Legacy22.x.x (22.0.0–22.6.0)23.x.x on June 30, 202724.x.x and 25.x.x
Android: GMA Next-Gen SDKNone0.x.x-alpha on June 30, 20271.x.x and 0.x.x-beta
iOS10.x.x11.x.x in Q2 202712.x.x and 13.x.x
Unity plugin8.0.0–8.7.09.0.0–9.6.0 in Q2 202710.0.0–10.7.0 and 11.x.x
Flutter google_mobile_ads3.0.0–4.0.05.0.0–5.3.1 in Q2 20276.0.0–7.0.0 and 8.0.0–9.x.x

Anything older was sunset in earlier years. Google's iOS timetable gives June 30, 2026 as the 10.x.x sunset date, though its status column still says Deprecated.

What sunset means

Sunset is a risk, not an instant switch-off: Google says traffic from a sunset version is at risk of automatic no fill and that it regularly reviews sunset versions to consider disabling ad serving, oldest versions with lower usage and higher maintenance costs first. Once serving is disabled, ad requests return no fill with an error indicating that the version is sunset. Deprecated and sunset versions get no technical SDK support. A Unity or Flutter plugin version counts as sunset once its Android or iOS dependency is.

What comes next

Find the SDK version you ship, and who still runs old ones

# Android: legacy is play-services-ads, Next-Gen is ads-mobile-sdk (use your module name)
./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep -E "play-services-ads|ads-mobile-sdk"
# iOS: CocoaPods, then Swift Package Manager
grep Google-Mobile-Ads-SDK Podfile.lock
find . -name Package.resolved -exec grep -A6 swift-package-manager-google-mobile-ads {} +
# Flutter
flutter pub deps | grep google_mobile_ads
# Unity: plugin version (OpenUPM install), then the native SDKs it pulls in
# (the dependencies file is under Assets/ for a .unitypackage install, inside the package for OpenUPM)
grep com.google.ads.mobile Packages/manifest.json
find . -name GoogleMobileAdsDependencies.xml -exec grep -E "play-services-ads|ads-mobile-sdk|Google-Mobile-Ads-SDK" {} +

At runtime: MobileAds.getVersion() on Android, string(for: MobileAds.shared.versionNumber) in Swift (SDK 12 or later), MobileAds.instance.getVersionString() in Flutter, MobileAds.GetPlatformVersion() in Unity.

To see who still runs old SDKs, add the GMA SDK and App version dimensions to the Ads Activity report in AdMob (for Android, GMA SDK data starts on August 3, 2023). In the AdMob API they are GMA_SDK_VERSION and APP_VERSION_NAME; neither works with ESTIMATED_EARNINGS or OBSERVED_ECPM, so measure requests and fill:

POST https://admob.googleapis.com/v1/accounts/pub-XXXXXXXXXXXXXXXX/networkReport:generate
{"reportSpec": {
  "dateRange": {"startDate": {"year": 2026, "month": 10, "day": 22},
                "endDate": {"year": 2026, "month": 11, "day": 20}},
  "dimensions": ["APP", "GMA_SDK_VERSION", "APP_VERSION_NAME"],
  "metrics": ["AD_REQUESTS", "MATCH_RATE", "IMPRESSIONS"]}}

Upgrade by platform

Android, legacy route. From 22.x or 23.x, the smaller step is play-services-ads 25.x.x (current: 25.5.0, September 17, 2026). Follow Google's v23, v24 and v25 migration sections in order: minSdk goes to 21, 23 and then 24 (from 25.5.0); 24.0.0 stops distributing firebase-ads and firebase-ads-lite (use play-services-ads); old APIs such as AdRequest.Builder.addTestDevice() are gone; 25.0.0 removes the onFailure(String) and onAdFailedToShow(String) mediation callbacks and updates the UMP SDK dependency to 4.0.0.

Android, Next-Gen route. com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk (current: 1.7.0, November 18, 2026) needs minSdk 24 and compileSdk 34 or higher, and must be initialized before loading ads, on a background thread, with the app ID passed in InitializationConfig; UMP still needs the app ID in AndroidManifest.xml. If you connect to AdMob through a third-party mediation platform that supports partner bidding, check Google's table first: it marks AdMost, TopOn, TradPlus VisiM and Unity LevelPlay compatible, and AppLovin MAX, Chartboost Mediation, DT Fairbid, Gravite and Nimbus not compatible.

dependencies {
    // remove: implementation("com.google.android.gms:play-services-ads:...")
    implementation("com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk:<version>")
}
// with mediation: adapters still depend on the legacy SDK, and Next-Gen includes the classes they need
configurations.configureEach {
    exclude(group = "com.google.android.gms", module = "play-services-ads")
    exclude(group = "com.google.android.gms", module = "play-services-ads-lite")
}

iOS. Go to 13.x.x (current: 13.13.0, November 16, 2026). 11.0.0 raises the deployment target to iOS 12 and Xcode to 15.1 and serves ads only on iOS 13 and later; 12.0.0 needs Xcode 16.0 and renames the Swift API (no GAD prefix, GAM becomes AdManager, GADM becomes Mediation); 13.0.0 raises the deployment target to iOS 13; per the release notes, 13.4.0 raises the minimum supported Xcode version to 26.2 (the quick start still lists Xcode 16.0). Move to Swift Package Manager now: run pod deintegrate if CocoaPods goes completely, then File > Add Package Dependencies with https://github.com/googleads/swift-package-manager-google-mobile-ads.git and the Up to Next Major Version rule. If you stay on CocoaPods, Google says Xcode 27 builds need its Podfile post_install hook, which sets every pod target's deployment target to iOS 15.0.

Unity. Go to plugin 11.x (current: 11.7.0, November 12, 2026, which adds Swift Package Manager support). 11.6.0 raises the minimum Unity version to Unity 2022 LTS (2022.3), which the changelog marks as a breaking change, and the minimum Android API level to 24. From 11.1.0 you can switch Android builds to Next-Gen in Assets > Google Mobile Ads > Settings by enabling Switch Google Mobile Ads Android Architecture and GMA Next-Gen SDK; since 11.3.0, Next-Gen needs MobileAds.Initialize() on the main thread.

Flutter. Go to google_mobile_ads 9.x (current: 9.2.0, October 21, 2026, with Android 25.5.0, Next-Gen 1.5.0 and iOS 13.11.0). 8.0.0 needs at least Flutter 3.38.1 and Dart 3.10.0 and adds Swift Package Manager support. From 9.0.0, Android can run Next-Gen: set the API levels above, exclude the gms modules if you mediate, build with --dart-define USE_NEXT_GEN_SDK=true and, for native ad templates, update the NativeAdFactory import and the NativeAdView class.

React Native. Google now documents its own Google Mobile Ads SDK for React Native, labeled Beta; it needs React Native 0.85.0, Android API level 24, iOS 13.0 and Xcode 16.0 or later. Its Other platforms page lists the third-party react-native-google-mobile-ads library and says such libraries are not official Google Mobile Ads SDKs and aren't covered by AdMob support. Either way, check the native SDK versions inside with the commands above.

Mediation adapters

Order of work so revenue does not drop

  1. Pull 30 days of the Ads Activity report by app, GMA SDK and App version. Fix apps with requests on sunset versions first, then deprecated ones.
  2. Pick one target per app: iOS 13.x on Swift Package Manager, Unity 11.x, Flutter 9.x. On Android, take legacy 25.x if your mediation platform isn't marked compatible with Next-Gen.
  3. Upgrade the SDK, every adapter and the UMP consent flow together on one branch, then test with test ads and the ad inspector: adapters initialize, the consent form shows, every format loads.
  4. Release to part of your users first (a staged rollout on Google Play, a phased release on the App Store) and compare match rate and impressions of the new GMA SDK version with the old.
  5. Prompt users off old builds (on Android, Play in-app updates) and watch requests from sunset versions shrink.
  6. If you stayed on legacy Android, ship Next-Gen as its own release before technical support for legacy 24.x.x and 25.x.x ends on June 30, 2027 (they sunset on June 30, 2028).
Still earning from an app on a sunset AdMob SDK? We update native, Unity, Flutter, React Native and Xamarin apps to current SDKs and store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer