Google Play — Target API level requirement
This is a technical gate rather than a policy judgement: Play requires new apps and updates to target a recent Android API level, and raises the bar every year.
What the rejection usually says
Your app currently targets API level and must target API level or higher.
You must update your app to meet the target API level requirement.
Wording varies between reviewers; the substance does not.
Why it gets triggered
- targetSdkVersion left behind while the deadline moved.
- A dependency that blocks upgrading.
- A build variant that lags the main one.
How to fix it
1.Raise targetSdkVersion
Update the value, then work through the behaviour changes for each level you skipped — storage, permissions and background limits are the usual work.
2.Test the behaviour changes
Scoped storage, notification permission, foreground service types and exact alarms are the common breakages.
3.Know what it affects
Existing installs keep working; the requirement blocks new submissions and updates, and eventually new-user discovery.
A reply you can adapt
Short, specific, and stating what changed — reviewers read hundreds of these.
Thank you. This build targets the current required API level, with the storage and notification-permission behaviour changes implemented and tested across the affected Android versions.
AppSubmit does this for your app, specifically
Paste the rejection and the decoder reads it against your actual listing, build and release history — then writes the fix plan and drafts the reply. It also watches your submissions, so the next rejection reaches you as a notification rather than a surprise.
Decode a rejection free