Google PlayAndroid 16App MaintenanceBusiness Owners

Can't Update Your Android App? Google Play's API 36 Rule, Explained for US Business Owners

Android update rejected by Google Play? The API 36 rule in plain English for US business owners: what changed, why apps fall behind and what the fix takes.

DeveloperMill6 min read

Your developer emails to say the Android update was rejected. Or you open Google Play Console and see a warning you don't understand. Or downloads have quietly dropped, and nobody can say why. For a lot of US businesses with an Android app, these all have the same cause: Google Play's target API level rule, and in 2026 the bar moved to API 36.

This guide explains the rule in plain English, why apps fall behind and what fixing it actually involves. If you're a developer looking for the technical steps, see our React Native and Expo API 36 migration guide.

Symptoms: how this shows up for your business

  • The update is rejected. Play Console refuses the upload with a message along the lines of "your app currently targets API level 34 and must target at least API level 36 to ensure it is built on the latest APIs optimized for security and performance."
  • Warnings in Play Console and email. Google sends notices ahead of each deadline, and Play Console flags apps that don't meet the target requirement. They're easy to miss if they go to a former employee's or agency's inbox.
  • Installs drop. New users on newer Android phones may not be able to find or install your app. Google Play tells them it isn't available because it was made for an older version of Android. Your existing users usually keep working, so the problem stays hidden.
  • You can't ship fixes. Even an urgent bug or security fix is blocked until the target API is updated.

The rules in plain English

Google's target API level requirements work like this:

Your situationWhat Google Play requires
Publishing a new app or any update (phones and tablets)Target Android 16 (API level 36) or higher, since August 31, 2026
An existing app you're not updatingTarget Android 15 (API 35) or higher to stay visible to new users on newer Android versions
Wear OS and Android Automotive appsTarget API 35 or higher

Google offered some developers an extension to November 1, 2026. That has now passed.

What "target API" means: it's the Android version your app says it was built and tested for. It's not the oldest Android version your app supports. Raising the target doesn't cut off customers on older phones. It tells Android your app follows the newest privacy, security and layout rules, which is why Google insists on it.

Why apps fall behind

Apps stuck on an old target API usually got there one of these ways:

  • The agency moved on. The app was built as a project, the contract ended and nobody was paid to maintain it. Google raises the bar every year, so an app nobody touches falls out of compliance within a year or two.
  • An old React Native or Expo version. Each framework version targets a specific Android version. Expo SDK 54 and later (React Native 0.81+) target API 36. An app still on an Expo SDK from 2023, or a React Native version from several years ago, can't simply flip a setting. It has to be upgraded through the versions in between.
  • Abandoned libraries. Maps, payments, chat or analytics libraries that stopped being updated can block the upgrade and need replacing.
  • Lost access. Nobody has the source code, the Google Play Console login or the app's signing key. This is the most painful version, and also the most fixable if you act before you need an urgent update.
  • A builder or wrapper platform that stopped updating its output. If your app came from an app builder, check whether it still produces compliant builds. Our guide to exporting code from an app builder covers what to do if it doesn't.

What the upgrade involves

Here's what a developer does to bring an older app up to API 36, in plain terms:

  1. Access check. Confirm you have the source code, Google Play Console access and the upload key. If your app uses Play App Signing, which apps published since 2021 generally do, Google can reset a lost upload key.
  2. Framework upgrade. Move the app to a current version of React Native or Expo, stepping through intermediate versions if it's far behind.
  3. Library updates. Update or replace libraries that don't support the new Android version, including older native code that doesn't meet Google Play's 16 KB memory page requirement.
  4. Permissions and policies. Newer Android versions changed how apps ask for notification, photo and location access and how background work runs. Google Play's Data safety form and account deletion requirements may also need updating.
  5. Layout fixes. Android 16 makes apps draw edge to edge and lets them rotate and resize on tablets and foldables. Screens that looked fine can end up under the status bar, or broken on larger devices.
  6. Testing. Sign-in, payments, push notifications, forms and key flows on real Android 16 devices, plus a tablet.
  7. Release. Upload to a testing track, review Google's pre-launch report, then roll out to users in stages.

Typical timelines

Starting pointTypical effort
Already on Expo SDK 54+ or React Native 0.81+1–3 days to rebuild, check and release
One to three framework versions behind1–2 weeks
Several years behind, with old native libraries2–6 weeks
Missing source code, accounts or signing keyAccess recovery first, sometimes a rebuild

These are typical ranges. App size, custom native code and how many third-party services the app uses all move the number. Our app maintenance cost guide explains how to budget for this kind of work every year.

What to do this week

  1. Log in to Google Play Console and check your inbox and policy status for target API warnings. In the app bundle explorer, the latest release shows which API level it targets.
  2. Check your access. Make sure your company owns the Play Console account and has the source code, and find out who holds the upload key.
  3. Get an assessment before you need an urgent fix. The cheapest time to upgrade is before a release is blocked.

If you need someone to do the work, our guide on how to hire a React Native developer covers what to look for, and we compare offshore vs US developers on cost.

Next year: API 37

This isn't a one-time fix. Google has said Play will require new apps and updates to target API level 37 (Android 17) in August 2027. The exact day hasn't been announced, but past deadlines have landed at the end of August. Android 17 is expected to bring more changes for tablets and large screens.

Plan to ship a compliant update by early summer 2027, and keep a small yearly maintenance budget so each deadline is a routine update instead of an emergency. iOS has a yearly cycle too. This year it's the iOS 27 scene lifecycle requirement.

Not sure where your app stands? Send us the link below and we'll tell you within 48 hours.

Frequently asked questions

Why was my Android app update rejected by Google Play?

The most common reason in late 2026 is the target API level rule. Since August 31, 2026, Google Play only accepts new apps and updates that target Android 16 (API level 36) or higher. If your app was built for an older Android version, Play Console blocks the update until a developer upgrades and rebuilds it.

What does target API level mean?

The target API level is the Android version your app declares it was built and tested for. It is not the oldest Android version your app supports. Raising the target to API 36 doesn't stop people on older phones from using your app. It tells Android your app follows the newest rules.

Will Google Play remove my app if I don't update to API 36?

No, not right away. Existing users keep the app. But apps that target lower than API 35 are hidden from new users whose phones run a newer Android version, so installs drop. You also can't publish any update, including bug or security fixes, until the app targets API 36.

How long does it take to update an old Android app to API 36?

It depends on how far behind the app is. An app already on a recent React Native or Expo version can often be rebuilt and tested in a few days. An app one to three framework versions behind usually takes one to two weeks. An app several years behind can take two to six weeks, and an app with missing source code or accounts needs access recovered first.

What if my original developer or agency is gone?

You can still update the app if you can get the source code, access to your Google Play Console, and the app's upload key or Play App Signing setup. If the app uses Play App Signing, Google can reset a lost upload key. A new developer can then take over the upgrade.

When is the next Google Play target API deadline?

Google has said Play will require new apps and updates to target API level 37 (Android 17) in August 2027. Based on past years, plan for the end of August 2027 and aim to ship a compliant update by early summer.

Get a free Play Store compliance check

Send us your app link and we'll tell you within 48 hours what it needs to meet Google Play's target API requirement.

Prefer to talk? Book a call