DEV Community

Israr Kundi
Israr Kundi

Posted on Originally published at israr-kundi.web.app

Your Play Update Is Blocked? Target API 36

Your Play Update Is Blocked? Target API 36

Meta description: Target API 36 is now required for Play Store updates. Why your update is blocked, what changed, and the minimum fix.

Your Play update is blocked because of target API 36. Since 31 Aug 2026, Google Play only accepts new apps and app updates that target Android 16, which is API level 36. If your app targets anything lower, Play refuses the update, even when nothing else about your app has changed.

The problem: "My app still works, but I can't update it"

You press upload and Play says no. Your app is still live, and the people who already have it can still open it and use it. But the new version with your fixes sits on your computer, and no update goes out. Nothing in your code broke — the rule changed under you.

Worse, if your app targets API 34 or lower, new users on newer phones cannot find it at all. Play hides it from them. Your app is not removed, but it stops reaching new people, and your existing users stay stuck on the old version.

The cause: a yearly bar that moved to Android 16

Every Android app declares a target API level. This year the bar moved to Android 16. From 31 Aug 2026, that is the line: target API 36, or no update.

Google did give extra time once. A one-time extension ran to 1 Nov 2026, and that date has passed, so that extension is no longer available.

Targeting API 36 is not only a number change. Three behaviour changes come with it. Edge-to-edge is enforced, so your content draws under the status bar and the navigation bar. Predictive back is on by default, so the old onBackPressed() handler never runs. And tablets ignore a portrait lock, so an app that only ever showed upright can turn sideways on a tablet.

The minimum fix: target API 36

  1. Check what your app targets now. In Play Console, open your app bundle or release and look at the target API level. If it is below 36, you have found the cause.
  2. Raise the target SDK to 36 in your app's Android build settings, then rebuild the app bundle. Do not change anything else in the same build — you want to know the target API change is what fixed the upload.
  3. Test the three behaviour changes on a real phone and a tablet before you upload. Open every screen and check nothing important sits under the status bar or the navigation bar. Press back on every screen where your app does something special, because the old back handler no longer runs. Turn a tablet sideways and check your screens still make sense.
  4. Upload the new bundle to Play and check the release goes through. If Play still refuses it, read the exact message — it will say what is still wrong.
  5. Put 1 Feb 2027 in your calendar. From that date, Play also blocks updates to apps targeting Android 15 or higher that do not support 16 KB page sizes on 64-bit devices. Check your app's 16 KB readiness before then, while you are already touching the target API level.

What NOT to do: do not keep uploading the same old bundle and hoping Play changes its mind. The rule is enforced at upload, so the same bundle fails the same way every time. Do not lower the target API level to dodge the behaviour changes either — a lower target is exactly what Play refuses. And do not rebuild the whole app or redesign screens in the same release. Fix the target level first, ship the update, then improve the design.

When to get help instead of fixing it yourself

Get help when the rebuild itself fails, or when the app crashes or misbehaves after you raise the target level. Get help too when your app has many screens and the edge-to-edge change touches all of them, or when the back-button behaviour is wired through your whole app. A developer can raise the target level, fix the screens that break, and check the 16 KB page support for you, without rebuilding the app from scratch.

If this is your app, contact me through https://israr-kundi.web.app

Top comments (0)