DEV Community

Tim
Tim

Posted on

Google Play's API 36 deadline passed — here's the extension and the upgrade checklist

#android #kotlin #gradle #mobile

On August 31, 2026, Google Play stopped accepting new apps and app updates that don't target Android 16 (API level 36). If you haven't upgraded yet, you're not reading a warning about the future — your next upload is already blocked.

The good news: there is a documented way to buy time. The bad news: it's a one-time extension to November 1, 2026, requested through a form in Play Console. It's not automatic, and November 1 is a hard date. If you're blocked, file the extension today — then do the work, because the extension is not a plan.

The rule, precisely

  • Phones, tablets, foldables: new apps and all updates must target API 36+. The block hits at submission in Play Console — even a one-line crash fix can't ship until targetSdk goes to 36.
  • Wear OS and Android Automotive: API 35+. Android TV and Android XR: API 34+.
  • Apps you never touch again don't vanish, but they stop being available to new users on devices running a newer OS than your target. An app left on API 34 quietly stops being installable on current phones — which looks identical to your install rate dying for no reason.
  • Permanently private apps restricted to one organization and internal distribution only are exempt.

Two companion gates ride the same deadline: apps using Play Billing must be on Billing Library 8.0.0+, and if you ship native code, Play starts refusing uploads without 16 KB page-size support on February 1, 2027. Check both while you're in there.

What actually breaks when you raise targetSdk to 36

Changing the number takes a minute. Everything after that is the work:

  1. Edge-to-edge is now mandatory. The opt-out is dead. Deprecated flags like systemUiVisibility and setDecorFitsSystemWindows(false) misbehave at target 36. Use enableEdgeToEdge() plus proper WindowInsets handling, and audit every screen for content hidden under system bars.
  2. Predictive back is default-on. If you still override onBackPressed(), migrate to the OnBackPressedDispatcher / BackHandler APIs.
  3. Orientation and resizability restrictions are ignored on large screens (sw ≥ 600dp). If you lock orientation, test on a tablet.
  4. 16 KB page sizes. Native libraries compiled for 4 KB pages fail on 16 KB devices. Check every .so with readelf -lW — every LOAD segment needs p_align of 0x4000.
  5. The toolchain moves together. You can't just bump targetSdk: AGP ~8.13, Gradle 8.13 (the documented pairing), Kotlin 2.x, compileSdk 36. Bump them in the safe order and keep a green build at each step.
  6. Billing v8 migration. enableOneTimeProducts() and the new query APIs are the most-reported breakage — outdated wrappers like old react-native-iap versions can pin an old billing client transitively, so check the resolved dependency tree, not just your declaration.

Per-framework gotchas differ: Flutter devs hit edge-to-edge insets and plugin native code; React Native devs hit the billing wrapper pin and Hermes/NDK alignment; Capacitor/Cordova devs often discover a plugin ships a 4 KB-aligned .so they never knew about.

The verification pass

After the upgrade, verify from the built artifact, not from your source constants:

aapt2 dump badging app-release.aab | grep -i targetSdk
./gradlew :app:dependencies | grep billingclient
readelf -lW path/to/every/arm64-v8a/*.so | grep LOAD
Enter fullscreen mode Exit fullscreen mode

Then test on a real Android 16 emulator — and if you ship native code, on a 16 KB system image too. The Play Console pre-launch report won't catch a page-alignment crash reliably.

The full checklist

I've packaged everything above into a complete upgrade kit — the 5-question blockage self-check, the extension-filing walkthrough (exact Play Console path), the toolchain matrix with safe step order, 8 behavior changes with copy-paste fixes, per-framework notes, the 16 KB verification commands, a 12-symptom breakage catalog, and the 7 mistakes that cost devs the most time: https://8286544375711.gumroad.com/l/yuwbzo

Disclosure: the kit is a paid $29 product. Everything in this article is free and standalone — the kit is for people who want the complete checklist in one place instead of assembling it from the docs.

(Independent guide — not affiliated with Google. Verify deadlines against the official target API requirements page; policy details evolve.)

Top comments (0)