Google Play Target API Level Requirement: Deadlines and How to Comply

Every year Google Play raises the minimum target API level. Miss it and you cannot ship updates; miss it for long enough and your app stops being discoverable to new users. This is the most predictable deadline in Android development and it still catches teams every year.

How the rule works

New apps and updates to existing apps must target an API level within one year of the latest major Android release. The cutoff lands on 31 August each year. A separate, later deadline applies to existing apps that are not being updated.

Because the rule is relative to the latest Android release rather than a fixed number, check the current required level in Play Console before planning — the console shows the exact level your app must meet.

What happens if you miss it

• You cannot upload new releases. Play Console rejects the bundle at upload with a target API error.
• Existing installs keep working. Your users are not cut off.
• After a further grace period, the app stops being available to new users on devices running newer Android versions — effectively invisible to most of the market.

Upgrading properly

Changing the number in build.gradle takes ten seconds and is the smallest part of the job. Each API level brings behaviour changes that apply as soon as you target it.

• Bump targetSdk one level at a time if you are several years behind. Jumping four levels at once makes failures impossible to attribute.
• Read the behaviour changes page for every level you pass through, not just the destination.
• Test on a device running that Android version, not only an emulator.

The changes that break apps most often

• Scoped storage — direct file paths outside app-specific directories stop working; you move to MediaStore or the Storage Access Framework.
• Background execution limits — background services and location access get progressively more restricted.
• Runtime permission changes — notification permission became runtime-requested, and several permissions now require a declared, reviewed use case.
• PendingIntent mutability — must be explicitly flagged, and crashes at runtime if not.
• Foreground service types — must be declared, and the declaration is policy-reviewed.
• Package visibility — you can no longer freely query which other apps are installed.

A safe upgrade sequence

• Upgrade compileSdk first and fix compilation and deprecation warnings.
• Update AndroidX and Play Services dependencies, which often carry the required fixes already.
• Raise targetSdk by one.
• Run your full test suite plus a manual pass over storage, permissions, notifications and background work.
• Ship to internal testing, then closed testing, then production.
• Repeat until current.

Do not leave it to August

The deadline is known a year ahead. Teams that upgrade in the spring ship calmly; teams that start in late August ship a rushed release into the busiest review queue of the year. Put the upgrade in a quarter, not a week.

Confirm the exact required API level and dates in Play Console Help before planning — Google publishes them annually and they move.