If Google Play is warning that your app needs a newer target API, the first job is not to guess at Gradle settings. First confirm what the current build actually contains.
What the warning usually means in 2026
For standard Android phone/tablet apps, new apps and updates submitted from August 31, 2026 must target Android 16 / API 36 or higher. If your current APK or AAB targets API 35, it needs a source-level update before the next standard submission.
Step 1: check the current APK or AAB
Record the package, versionCode, versionName and target SDK. If you do not use Android Studio, the compiled artifact can still provide this information.
Step 2: do not confuse submission readiness with existing availability
An existing standard app targeting API 35 meets the separate 2026 availability threshold described by Google for new users on newer Android devices. That does not make an API 35 build ready for your next normal update after the API 36 submission deadline.
Step 3: find the real source project
The normal repair path needs source code. The compiled APK/AAB can diagnose release facts, but safe migration of build tools, dependencies and code should happen in the source project.
Step 4: build before broad changes
Make an isolated copy and establish whether the project can clean-build. If the build system is already broken, solve that first and record the exact error rather than stacking multiple migrations on top of an unknown baseline.
Step 5: migrate compile and target SDK deliberately
Android’s current Android 16 setup guidance uses compileSdk 36 and targetSdk 36. Raising target SDK also means testing the app against Android 16 behaviour changes rather than only editing a Gradle number.
Step 6: check dependencies and native code
Old SDKs can block a migration. If the artifact contains native .so libraries, add a 16 KB compatibility check as a separate release gate.
Step 7: build and validate the replacement
After the source is repaired, build a fresh release artifact and confirm:
- same intended package/application ID;
- new valid versionCode;
- target/compile SDK expected for the release;
- expected resources and manifest;
- correct signing/upload process;
- install and launch tests;
- regression tests for changed functionality.
How difficult is the repair?
A clean Java/Kotlin project with maintained dependencies can be much easier than an old project with a broken Gradle build, abandoned SDKs, native libraries or major Android behaviour assumptions. That is why an initial artifact check can show the problem class, while the source assessment determines whether the fixed Standard or Advanced tier applies. If neither tier safely fits the job, Studio declines it.
Does fixing API 36 guarantee Play approval?
No. It solves one important submission requirement. Google Play still evaluates other technical and policy requirements.
Last verified: 17 August 2026
Official references
Need the facts from your APK or AAB?
Use the free Studio checker to read the important release facts directly from the compiled artifact. You do not need Android Studio or Android development knowledge.
Analyze APK / AAB →