Every August, Google Play raises the minimum target API level for apps in the store. If you have not updated your app to that new target SDK by the deadline, any new release you try to push gets rejected. Existing builds stay live for a window, but you cannot ship updates, fixes, or new features until you catch up.
For solo devs this one is brutal because it does not announce itself in your dashboard. The Play Console just starts refusing your release with a message that almost looks like a normal validation error.
Here is what usually breaks first.
Your build.gradle is locked to an older target
Most Android Studio templates write a targetSdk value into the app module build.gradle the day you create the project. Nobody touches it after that. Two years later it is still pointing at the same number, and now Play wants something higher.
The fix is one line:
defaultConfig {
targetSdk 34
}
The trap is that bumping targetSdk usually breaks behavior. Background work, scoped storage, notification permission prompts, exact alarms, all of these change with API level. You bump the number, you also need to do the migration work.
You also need to update compileSdk
Google Play checks targetSdk, but you will run into runtime crashes if compileSdk is older than the libraries you depend on. AndroidX, Compose, and a lot of Google Play services updates pin newer compileSdk values. Update both at the same time.
App Bundle uploads do not auto-rebuild
If you uploaded an .aab and then bumped target SDK in code, the .aab on Play is still the old one. You have to upload a fresh build. Sounds obvious until you spend an afternoon wondering why the warning is not going away.
Beta and internal tracks have the same rule
The deadline is not just for production. Internal testing, closed testing, and open testing tracks all enforce it once the cutoff hits. So you cannot work around it by demoting your app to a test track.
How to spot it before it bites
Set a recurring reminder in May or June every year. Google announces the new target SDK requirement months ahead. Read the Android Developers blog post when it lands. Bump your project before July, push a test build, leave a couple of weeks to fix migration issues.
If you are juggling several apps, this becomes a real chore. Built IOn Emit to flag the target SDK gap before you hit the Play Console, alongside the data safety form, signing key checks, and the rest of the release checklist. Freemium so you can try the core checklist for free. https://theionproject.com/ionemit
Anyone else been caught by the August cutoff? Curious how others batch the target SDK migration across multiple apps.
Top comments (0)