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

On August 31, 2026, Google Play ceased accepting new apps and updates that did not target Android API level 36. Those who have not completed the upgrade are already experiencing blocked submissions. A documented extension exists, but it is a one-time offer until November 1, 2026. Apps remaining on lower targets will no longer be installable on devices running newer OS versions.

The deadline impacts not only new apps but also existing ones, which will stop being available to new users. Apps using Play Billing must be on version 8.0.0 or higher, and native code uploads will be rejected without 16 KB page-size support starting February 1, 2027. Upgrading targetSdk to 36 is just the beginning; additional work is required.

Changes include mandatory edge-to-edge support, obsolete deprecated flags, default predictive back functionality, and ignored orientation/resizability restrictions on large screens. Native libraries compiled for 4 KB pages will fail on devices with 16 KB page sizes. To ensure a smooth transition, developers must update the Android Gradle Plugin, Gradle version, Kotlin version, and compileSdk to 36, in the correct order.

Billing version 8 migration is crucial, with new APIs and wrapper updates impacting various development frameworks. After the upgrade, developers must verify the built artifact using specific commands and test on a real Android 16 emulator, particularly if native code is involved. The final section of the article provides a comprehensive upgrade checklist, covering self-check questions, extension filing, toolchain matrices, behavior changes, per-framework notes, a catalog of common breakage symptoms, and common mistakes that can cause significant delays during the upgrade process.