Google Play target API level requirements policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for New Android submissions, app updates, and existing apps available to new users.
An outdated target API can block an update or limit an existing app’s availability. Google’s requirements differ between new submissions and existing apps, so check which case the notice describes.
What to check
Read the target SDK in the release artifact, not just a local configuration file. Check Google’s linked deadline table for the current required API level, applicable deadline, and any available extension.
The target API level isn’t the minimum Android version your app supports. Raising the target can change permissions and platform behavior without requiring the same increase to the minimum version.
How to address the rejection
Update your framework and dependencies as needed, set the required target, and test the Android behavior changes that apply. Pay particular attention to permissions, notifications, background work, and edge-to-edge layout.
Upload the corrected artifact to the intended track and verify its target in Play Console. Avoid hard-coding an old deadline into your release checklist: Google updates these requirements, and the official schedule is the reference for your submission.
Messages this guide can help with
Target API level requirements; Target API level requirements policy violation; Target API level requirements rejection; Target API level requirements denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Target API level requirements Checked 22 September 2026