Guides

Google's target API warning: what it means, what to do

What the Google Play target API warning means: the August 31 deadline, the November 1 extension, what breaks if you miss it, and what to do this week.

Aiden Sung, MyQuietSpotUpdated 5 min read

You got Google's target API warning. Here's what it means and what to do

If Play Console is showing a warning on the Policy status page that says your app must target a newer API level, you are not alone, and it is not an emergency yet. It is a deadline. We meet the same deadline for 17 apps of our own every summer; because all of them inherit their target API level from one shared toolchain, meeting it is one upgrade and a rebuild per app, and then a real-device check of every release build. Here is what the Google Play target API level warning actually means, what happens if you miss it, and what to do this week.

What "target API level" means in plain words

Every Android app declares which version of Android it was built and tested for. That is the target API level. Google raises the minimum every year so that apps keep up with security and privacy changes in the operating system.

The app still runs on older phones. Targeting a newer API doesn't drop old devices; that is a separate setting (the minimum API level). What it changes is how the app behaves on new devices, because each Android version adds rules that only apply once you target it.

The dates for 2026

From Google's page on target API level requirements:

  • By August 31, 2026: new apps and app updates must target Android 16 (API level 36) or higher. Wear OS and Android Automotive apps need API 35; Android TV and Android XR apps need API 34.
  • By August 31, 2026, existing apps that aren't being updated must target at least Android 15 (API level 35). Otherwise they stop being available to new users whose devices run a newer Android version than the app targets.
  • Extension: you can request an extension to November 1, 2026. The form is in Play Console, on the Policy status page, through the details page of the warning.

The same page lists August 31, 2025 and API level 35 for the previous round, so the number has gone up by one a year. If you are reading this later, check the current numbers on that page rather than trusting ours.

What happens if you miss it

Two different things, and it helps to keep them apart.

You get stuck. You can't publish an update that targets an old API level. That's the immediate pain: a bug you need to fix, or a feature you paid for, can't ship until the target API is fixed first.

New users on new phones can't find you. For existing apps below the required level, Google says the app becomes unavailable to new users whose devices run a newer Android version than the app targets. Users who already installed it are not affected; they can still find it, reinstall it, and use it. Your app doesn't vanish for them. It just quietly stops growing on the newest phones.

Google's page does not describe the app being deleted from the store for this reason. If someone tells you your app "will be removed on August 31," ask them to show you where Google says that.

Why it is more than changing a number

Technically, raising the target API is one line in a build file. Practically, it is the moment every behavior change in the new Android version switches on for your app. Notification permissions, background limits, how files and photos are accessed, what the system does with alarms: each version changes some of these.

Two other things ride along with the same rebuild:

16 KB page sizes. Since November 1, 2025, new apps and updates that target Android 15 or higher must support 16 KB memory page sizes (Android Developers Blog). Google's documentation now also says that starting February 1, 2027, updates that don't support it can't be released (Support 16 KB page sizes). If your app, or any library inside it, contains native code, that library may need updating. The dates around this requirement have shifted; check the current date on Google's page.

Release-build surprises. This is the part we learned the hard way. One version of our own kombucha-brewing app passed every check on the emulator, then shipped with no working notifications at all. The release build's resource shrinker had removed the notification icon because only Dart code referenced it, so the notification plugin never initialized. The app looked healthy. Two other apps of ours crashed only in release builds on real devices because of missing ProGuard rules. Neither problem shows up in a debug build. Our pre-release check now refuses a build without those rules, and whoever does your target API update should install the actual release build on a real phone and press the buttons.

If you are not the developer

You don't need to understand the build file. You need three answers from whoever maintains the app:

  1. What API level does the app target now, and what will it target after the update?
  2. Does the app contain native libraries, and are they 16 KB compatible?
  3. Will you test the release build on a real device before submitting, and can I see a screenshot of a notification working?

If your developer has stopped responding, that's a different problem, and we wrote about it separately: what to do when your app developer disappears.

What to do this week

  • Open Play Console and note the exact warning text and the date it gives for each app.
  • Find out your app's current target API level (ask your developer; the warning itself states the level Google wants).
  • Decide who is doing the update, and get a date from them that is before August 31, not on it.
  • If the date can't be met, request the extension to November 1 now, while the form is available.
  • Ask for the release build to be tested on a real phone, not just an emulator.

If nobody is watching these dates for you, App Care does exactly that. It is the same summer routine we run on our own 17 apps, with the same pre-release check in front of every build.

Sources

FAQ

What is the Google Play target API level deadline for 2026?

August 31, 2026. New apps and updates must target Android 16 (API level 36). Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer devices. An extension to November 1, 2026 can be requested in Play Console.

Will my app be removed from Google Play if I miss the deadline?

Google's page does not describe removal. It says the app becomes unavailable to new users whose devices run a newer Android version than the app targets. Users who already installed it keep it. You also can't publish updates until you comply.

How do I request the extension?

In Play Console, open the Policy status page, open the details page of the target API warning, and use the extension form there. Google's developer page says the extension forms become available in Play Console later in the year.

Is raising the target API level just changing a number?

No. Each Android version changes how apps behave (permissions, background work, notifications). The app must be rebuilt and tested as a release build on a real device. Apps with native libraries also need 16 KB page-size support.

Related

6 min

How we keep 17 apps of our own alive on both stores

The yearly checklist we use to keep 17 Flutter apps live on the App Store and Google Play: deadlines, release-build traps, and what to check this week.

app maintenance · app store requirements · google play · checklist

← All guides