Google Play target API level requirement

How to update your target API level

Follow these steps in order. Each one is something we do on client work.

1. Check the current requirement. Play Console Help lists the target API level new apps and updates must meet now and in the future.
2. Update targetSdkVersion. Raise it in your Gradle config and update the Android Gradle Plugin and dependencies that need it.
3. Read the behaviour changes. Each Android version changes permissions, background work and notifications. Test the ones you use.
4. Test on a current device or emulator. Run the full flow: install, login, purchase, notifications.
5. Upload a new bundle. Increment versionCode, then roll out to a test track first.
6. Watch the deadline banner. Play shows when an existing app falls out of compliance and stops being available to new users.

Google Play target API level: key rules and context

What the rejection means. Google publishes the requirement and deadlines on Target API level requirements. Older apps can also become hidden from users on newer Android versions.

Why it usually happens

• The app wasn't updated for a year or more.
• A dependency blocks raising targetSdkVersion.
• An extension deadline passed.

How to fix it

1. Check the current required level on Google's page.
2. Update compileSdk and targetSdk, and dependencies.
3. Read the behaviour changes for each skipped Android version and test them (permissions, notifications, background work).
4. Submit the update.

Appeal or resubmit? This isn't an appeal case. Update, or request an extension in Play Console if offered.

How to avoid it next time. Schedule a target API bump each year after Google announces the new requirement.

Common mistakes

• Bumping the number without testing. Behaviour changes can break features quietly.
• Ignoring library updates. Old libraries may not support the new target.
• Waiting for the deadline. Updates get blocked once you miss it.
• Skipping a test track. Catch regressions before users do.

If you want this handled for you, our pricing page lists every fixed package.

Worked example (hypothetical)

This example is illustrative. The app is made up, and so are any numbers in it.

Say ShiftLog, a work-hours tracker, is blocked from updating because it targets an older API level. Raising the target changes how its exact alarms behave. We'd update the target, add the permission flow the newer Android version requires for that feature, test reminders on an emulator running the newer version, and roll out to internal testing for a few days before production.

Google Play rules that trip most apps

These come from Play Console Help pages we checked on 26 October 2026.

Checklist

Copy this list into your release notes or ticket and tick each item off before you ship.

• Current requirement read in Play Console Help
• targetSdkVersion raised
• Dependencies updated
• Behaviour changes tested
• versionCode incremented
• Internal test before production

Sources

• Google Play Console Help: Target API level requirements (accessed 26 October 2026)
• Play Console Help: Create and set up your app (accessed 26 October 2026)
• Play Console Help: Metadata policy (accessed 26 October 2026)
• Play Console Help: App testing requirements for new personal developer accounts (accessed 26 October 2026)
• Play Console Help: Add preview assets to showcase your app (accessed 26 October 2026)