Google Play requires Android 16 (API 36): what to do if your app is blocked

Since August 31, 2026, Google Play has rejected any new app and any update that does not target Android 16 (API 36). If your update is blocked, you need to raise the Android version your app targets, update its dependencies, then test the new behaviors enforced by Android 16 before resubmitting it. Your app is not removed from the store, but until this work is done, you can no longer ship a fix or a new feature.

This article explains, as of October 2026, exactly what Google requires, how to tell whether you are affected and how to get out of it, even if the developer who built the app is gone.

What exactly has Google Play required since August 31, 2026?

Google Play has required every new app and every phone and tablet update to target Android 16 (API 36) since August 31, 2026. Other device categories and apps that are not updated have lower thresholds.

The target API level (targetSdkVersion) is the Android version an Android app declares it was designed and tested for. According to the Android Developers documentation, Google raises the minimum accepted on the Play Store every year. As of October 2026, the rules are as follows.

Private apps distributed only internally within an organization are exempt.

The extension until November 1, 2026

Google Play lets you request extra time to target API 36, until November 1, 2026. According to Play Console Help, the form is sent to affected apps through Play Console notifications. As of October 15, 2026, this deadline is imminent: don't wait.

The "16 KB" requirement for apps with native code

The Google Play 16 KB requirement obliges apps that target Android 15 (API 35) or higher to support 16 KB memory pages on 64-bit devices. According to the Android documentation on 16 KB page sizes, starting February 1, 2027, updates that do not meet this rule can no longer be published.

This requirement affects apps that ship native code (C or C++), directly or through a third-party library. An app written only in Java or Kotlin, libraries included, is already compatible according to Google, although testing is still recommended.

By moving to API 36, your app automatically falls within the scope of the 16 KB rule. You might as well handle both at once.

How do you know whether your Android app is affected by the API 36 requirement?

An Android app is affected if it does not yet target Android 16 (API 36) and you need to update it on Google Play. Three signals should alert you.

• A warning in the Play Console. According to Play Console Help, only non-compliant apps receive a warning and a notification in the Play Console.
• An update rejected on upload. When you upload the app's new file, the Play Console shows an error stating that the app must target a higher API level. Publishing is blocked until this is fixed.
• An unexplained drop in new installs. If your app still targets Android 14 or lower, it is already no longer offered to new users with recent devices.

If you don't have access to the Play Console, that is the first problem to solve. The developer account normally belongs to your company. If it was created in the name of a former contractor or an employee who has left, recover administrator access before anything else.

What happens if you don't update your app to API 36?

An Android app that does not target API 36 stays on Google Play, but no new version can be published. According to Play Console Help, as of October 2026:

• the app stays on the store and existing users keep using it;
• it can still be reinstalled by those who already had it;
• every new version is rejected, including an urgent security fix;
• if it targets Android 14 or lower, it disappears for new users on more recent devices.

The risk builds up over time: at the first blocking bug or the first vulnerability discovered, you can no longer fix anything. And your user base erodes as people replace their phones.

How do you update an Android app to API 36?

Updating an Android app to API 36 almost always takes more than changing targetSdkVersion: you need to update the tools and libraries, adapt the app to Android 16 behaviors, then test. Here are the actual steps.

1. Update the tools and dependencies

The app must be compiled with the Android 16 SDK. This often means updating the build tools (Gradle, Android Gradle Plugin), then the framework in use: React Native, Expo, Capacitor, Ionic or Flutter. Every third-party library must be compatible. A library abandoned by its author must be replaced.

The more versions behind the app is, the longer this step takes.

2. Handle the Android 16 behavior changes

When an app targets Android 16, the system changes some rules. The main points, according to the Android documentation on Android 16 behavior changes:

• Edge-to-edge display. Edge-to-edge is the mode in which the app draws behind the status bar and the navigation bar. On Android 16, it can no longer be disabled. Without adjustments, buttons or text can end up hidden.
• Large screens. On screens with a smallest width of at least 600 dp (tablets, unfolded foldables), Android ignores orientation, resizability and aspect ratio restrictions. Games are exempt. A temporary opt-out exists, but it will no longer apply once apps target API 37.
• Predictive back. Back gesture animations are enabled by default on Android 16, and the old back button handling method is no longer called. Navigation that has not been adapted may behave unexpectedly.
• Health data. Apps that use body sensors must switch to new, more granular permissions.

3. Check 16 KB compatibility

If the app contains native code, each affected library must be checked and recompiled or updated if needed.

4. Test, then publish

Test on several screen sizes and Android versions, then submit the update for review. Final approval is up to Google: no one can guarantee a review time or outcome.

How do you update an old app if the developer has left?

An old app can be updated by a new developer as long as you recover the source code, Play Console access and signing keys. This is a common situation: the app works, no one has touched it in two or three years, and the original contractor can no longer be reached.

Before you start, gather:

• the complete source code, ideally in a Git repository;
• administrator access to the Play Console;
• the app's signing keys, or confirmation that signing is managed by Google (Play App Signing, the service in which Google stores the app's signing key);
• access to third-party services: backend, push notifications, analytics, payments.

If any of these is missing, an audit measures the gap and helps you choose between a simple update and a partial rebuild. An app far behind on its framework sometimes needs a full version upgrade rather than a targeted fix.

What steps unblock an app on Google Play?

Unblocking an app on Google Play takes ten steps, from checking the target version to publishing and monitoring.

1. Check your app's current target version and the warnings in the Play Console.
2. If you are still within the deadline, request the extension until November 1, 2026.
3. Recover the source code, Play Console access and signing keys.
4. Inventory the framework and libraries, with their versions.
5. Update the build tools, the framework and the dependencies to target API 36.
6. Fix edge-to-edge display, large screens and the back gesture.
7. Check 16 KB compatibility if the app contains native code.
8. Test on phones, tablets and several Android versions.
9. Publish, then monitor feedback and crash reports.
10. Plan for the next deadline: Google raises this minimum every year.

Who can bring your app into compliance with Google Play?

GUIGUI Tech offers Google Play and App Store compliance starting at €2,500 excl. VAT, over 1 to 3 weeks depending on the app's condition, including when the original developer has left. For an Expo or React Native app that is far behind, an Expo SDK and New Architecture upgrade may be a better fit, and the React Native audit at €1,500 excl. VAT gives you an assessment first.