Play Store & App Store publishing
Upgrade Your App to Target Android 16 (API Level 36)
Google Play stopped accepting updates below API 36 on 31 August 2026. Here is what that costs to fix, how long it takes, and what actually breaks.
Delivered in 2-4 working days
Fixed price · one-time · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹2,999Secure checkout with your package name.
- We upgrade and testShare the source on WhatsApp; we upgrade the tooling, fix what breaks and test on Android 16.
- ReleaseSigned AAB delivered, and released to Play if you want, within 2-4 working days.
The short answer
ZoopCoder upgrades an Android app to Android 16 (API level 36) — the target API level Google Play now requires — for a fixed ₹2,999, delivered in 2-4 working days. Google Play stopped accepting new apps and app updates below API 36 on 31 August 2026, so an app still on API 34 or 35 cannot ship a single update, not even a one-line bug fix; the only documented reprieve is an extension form in Play Console that moves your own deadline to 1 November 2026 and no further. The upgrade is rarely a one-line change: targeting API 36 disables the edge-to-edge opt-out attribute, turns predictive back on by default so onBackPressed is never called, and ignores fixed orientation and aspect-ratio locks on any display 600dp wide or more — which is why an app that still compiles fine can come back looking broken.
What you get
- compileSdk and targetSdk raised to 36 (Android 16)
- Android Gradle Plugin, Gradle, Kotlin and AndroidX libraries updated to versions that build against API 36
- Build errors, deprecations and manifest issues fixed
- Edge-to-edge insets applied so content is not hidden behind the status and navigation bars
- Predictive back migrated to the supported APIs, or a documented manifest opt-out if migration is not possible yet
- Orientation and aspect-ratio behaviour checked in a 600dp-wide window (tablet / foldable / desktop mode)
- Native libraries checked for 16 KB memory page-size support
- Tested on a real Android 16 device
- Signed release AAB, and the release submitted to Play Console if you want
| Price | ₹2,999 (fixed) |
|---|---|
| Target API level | 36 (Android 16) |
| Play deadline for new apps and updates | 31 August 2026 — already in force |
| Extension available until | 1 November 2026, requested in Play Console |
| Wear OS and Android Automotive OS | API 35 minimum |
| Android TV and Android XR | API 34 minimum |
| Apps left below API 35 | Stay installable only on devices running Android at or below the app's own target |
| 16 KB page-size deadline | 1 February 2027 for app updates (affects native/NDK code only) |
| Main behaviour changes handled | Edge-to-edge, predictive back, adaptive layouts, elegantTextHeight |
| Timeline | 2-4 working days |
| Deliverable | Signed AAB + updated source |
| Support | 15 days |
What we need from you
- App source code (native, Flutter, React Native or Cordova)
- Upload keystore or Play Console access
Not included
- Rewriting apps built on abandoned frameworks or unmaintained SDKs (quoted after inspection)
- Rebuilding native/NDK libraries that have no 16 KB page-size build (quoted after inspection)
- New features or redesigns
- Any guarantee about Google review outcomes — we control the build, Google decides the review
About this service
Google Play raises the minimum target API level every year, and on 31 August 2026 the bar became Android 16 (API level 36). Falling behind is not a warning you can dismiss — Play Console blocks the upload itself, so a security patch, a price change and a crash fix all sit in the queue until the app is upgraded. If you need breathing room, Google lets you request an extension in Play Console that moves your deadline to 1 November 2026; that is the whole reprieve, and it does not repeat. Most of the real work is in what API 36 switches on: enforced edge-to-edge (the opt-out attribute is deprecated and ignored on Android 16 devices), predictive back becoming the default so onBackPressed is no longer called at all — the single most common reason a WebView or wrapper app loses its back button after an upgrade — orientation and aspect-ratio locks being ignored on displays 600dp and wider, and the elegantTextHeight attribute being dropped, which shifts line heights in Tamil, Telugu, Kannada, Malayalam, Odia and Gujarati text. We update the build tooling, fix what breaks, test on a real Android 16 device and hand back a signed AAB. Older Cordova or long-abandoned projects sometimes need more than this, and we inspect and say so before taking the job. This is the recurring, unavoidable side of owning an app — our website and app maintenance cost guide puts an honest yearly number on it.
Questions before you buy
What does "your app must target Android 16 (API level 36) or higher" mean?
It is Play Console rejecting your upload, not your app crashing. Your build declares targetSdk 34 or 35 and Google Play will not accept it. Raising targetSdk to 36, fixing what that changes, and re-uploading is the whole fix.
What was the targetSdk 36 deadline?
31 August 2026. From that date new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play, except Wear OS and Android Automotive OS apps (API 35) and Android TV and Android XR apps (API 34).
What happens if I never upgrade?
You cannot publish any update. Separately, an existing app below API 35 stays available only on devices running a version of Android at or below its own target level, so it quietly stops reaching new users on current phones.
Can I still get more time?
Yes, once. Google's published policy is that you can request an extension through a form in Play Console that moves your deadline to 1 November 2026. It is a one-off extension, not a renewable one.
Why does my app look different after targeting API 36?
Android 16 enforces edge-to-edge and the old windowOptOutEdgeToEdgeEnforcement attribute is deprecated and disabled, so your layout now draws under the status and navigation bars. The fix is to apply window insets properly, which is included here.
My back button stopped working after the upgrade — why?
For apps targeting API 36 on an Android 16 device, predictive back is on by default: onBackPressed is not called and KEYCODE_BACK is not dispatched. Apps that intercepted the back key — WebView wrappers especially — need migrating to the supported back APIs, or a temporary manifest opt-out. Both are included.
Does this apply to Flutter, React Native and WebView wrapper apps?
Yes. The target API requirement is about what the Android build declares, not how the app was written, so Flutter, React Native, Cordova and plain WebView wrapper apps are all subject to it.
What is the 16 KB page-size requirement and do I need it?
Apps targeting API 35 or higher must support 16 KB memory page sizes on 64-bit devices, and from 1 February 2027 Google Play will not accept updates that do not. If your app is pure Java or Kotlin it already complies; only apps with native/NDK libraries need rebuilding. We check and tell you which case you are in.
Often ordered with this
© 2026 ZoopCoder