This is the most mechanical block on either store: a number in your build against a published floor. The real work isn't the number — it's the Android 16 behavior changes the higher target opts you into (edge-to-edge enforcement, predictive back, orientation locks ignored on large screens). Raise the target and test, in that order.
Got the actual message? Paste it into the free rejection decoder — it matches your rejection against documented store rules and returns the fix steps, the resubmission checklist, and a reply draft. Three free decodes, no account.
Target API Level Requirement — Target API Level Requirement (Play Console Help)
Your build targets an Android API level below Google Play's current floor, so Play Console blocks the submission before review even starts. Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher — Wear OS and Android Automotive OS must target API 35+, Android TV and Android XR API 34+. Separately, existing apps must target API 35 or higher to remain available to new users on devices running a newer Android version than the app targets.
Severity: blocker · Decoder confidence for this class: A (see the honesty note below)
The fix
- Raise targetSdkVersion (and compileSdk) to 36 or higher in your build configuration and rebuild.
- Work through the Android 16 behavior changes that apply at API 36 — edge-to-edge is enforced, onBackPressed is no longer called on Android 16 devices, orientation/resolution locks are ignored on tablets and foldables.
- Upload the new build to your release track; the block clears when the uploaded bundle targets the required level.
- If you genuinely cannot make the date, request the extension in Play Console — it moves the deadline to November 1, 2026, once, and does not renew.
Resubmission checklist
- Uploaded bundle targets API 36+ (or your form factor's floor)
- Android 16 behavior changes tested on a real device/emulator
- No older low-target builds left active on other tracks causing warnings
Reply draft
This is an automated Play Console submission block, not a review decision — there is no appeal form for it. Fix the target API level in the build and upload a new release; the block clears on upload. If you filed the extension request, note the November 1, 2026 date in your release calendar.
What the decoder can diagnose here: The exact floor for your form factor and whether you're blocked on submission (new/updates) or on discoverability (existing app left behind). This is a deterministic check — no reviewer judgment involved. What it cannot: Which Android 16 behavior changes will break your app when you raise the target (edge-to-edge enforcement, predictive back replacing onBackPressed, orientation locks ignored on large screens are the common ones). Test after raising; raising the number without testing trades a block for crash rejections.
Rule text: “New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play... Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running Android OS higher than your app's target API level. You will be able to request an extension to November 1, 2026 if you need more time.” — Play Console Help, 'Target API level requirements for Google Play apps', retrieved 2026-10-23
Frequently asked questions
What API level does Google Play require in 2026?
New apps and app updates must target Android 16 (API level 36) or higher since August 31, 2026. Wear OS and Android Automotive OS must target API 35 or higher; Android TV and Android XR, API 34 or higher.
What happens if my existing app targets a lower API level?
Existing apps must target API 35 or higher to remain available to new users on devices running a newer Android version than the app targets. Below that floor, new users on newer devices stop seeing the app.
Can I get an extension on the target API deadline?
Google offered a one-time extension to November 1, 2026 for apps that couldn’t make the August 31, 2026 date, requested in Play Console. It does not renew.
Is the target API level block something I can appeal?
No. It’s an automated Play Console submission block, not a review decision, so there is no appeal form. Raise targetSdkVersion (and compileSdk) to 36 or higher, test the Android 16 behavior changes, and upload a new build — the block clears on upload.
Related guides
- Rejection decoder — Google Play mode included
- Google Play Pre-Flight — the checks and the enforcement ladder
- App Store Pre-Flight — the other store's rulebook
- Play — Permissions declarations
Sources
- Play Console Help, 'Target API level requirements for Google Play apps', retrieved 2026-10-23
Last updated November 3, 2026. Rules change; the retrieval dates above say when this page was last checked against the store's published text.
Decode your rejection — free
The decoder covers 41 documented rejection patterns across the App Store and Google Play, grounded in the stores' own published rules. Three free decodes; the $29 Pre-Flight Founding pre-sale unlocks unlimited decoding plus a full pre-flight check credit when the checker ships.
The decoder classifies and guides from the message you paste. It cannot see your app or your binary, and it never promises an approval outcome — that decision is always the store's.