Your Android App Missed the Target API Deadline? What Happens Now and How to Fix It

Short answer: Since 31 August 2026, Google Play only accepts new apps and app updates that target Android 16 (API level 36). Google let developers ask for an extension to 1 November 2026, and that date has passed. Your live app can stay on Play, but you cannot ship any update, even a bug fix, until the app targets API 36.

This guide is for businesses that own a customer app, a staff app or a field service app on Google Play, and that rely on a developer or agency to keep it running.

What the rule says

Google's Play Console Help page on target API level requirements sets two different rules:

Wear OS, Android TV, Android Automotive OS and Android XR apps have lower targets. Permanently private apps used only inside one organisation are exempt.

What happens to your app now

There are two separate effects, and many teams only notice the first one.

1. You cannot ship updates. Any new version you upload must target API 36. Until it does, a security fix, a price change or a new payment option cannot go out.
2. New users may stop seeing the app. If your live app targets Android 14 (API level 34) or lower, Google says it is only available to devices running the same Android version or lower. New customers on newer phones will not find it on Play.

Users who already installed the app can usually keep using it. The risk is that you are stuck the moment something needs fixing.

How to check where you stand

1. Open Play Console and go to your app's dashboard. Look for policy notices about target API level in your Inbox or Policy status.
2. Ask your developer for the targetSdkVersion in the app's build file.
3. Check whether your app had an extension. If it did, it ended on 1 November 2026.
4. List any updates you have been waiting to ship, so you know what is blocked.

What usually breaks when moving to API 36

Changing one number in the build file is easy. Testing what changes with it is the real work. Google's Android 16 behavior changes page lists several that affect business apps:

• Edge to edge is enforced. Apps targeting API 36 can no longer opt out of drawing behind the status bar and navigation bar. Buttons and headers can end up hidden under system bars if the layout was not updated.
• Back navigation changes. Predictive back animations are on by default on Android 16 devices, and the old onBackPressed method is no longer called. Apps that catch the back button, such as checkout or form screens, need a fix.
• Large screens ignore orientation locks. On tablets and foldables with a smallest width of 600dp or more, fixed portrait or landscape settings no longer apply. A portrait only layout may stretch badly.
• Font height setting is ignored. The elegantTextHeight attribute no longer works. If your app shows Arabic text, check that lines are not clipped.

Libraries and SDKs also need updates, for example payment, maps, chat and analytics SDKs. Old versions may not support API 36.

A 2 to 4 week update plan

1. Week 1: Audit. Update the build tools and libraries, set the target to API 36 on a branch, and list every warning.
2. Week 2: Fix. Work through edge to edge layouts, back handling and large screen layouts.
3. Week 3: Test on real devices. Use at least one Android 16 phone, one older phone you still support and one tablet. Test login, payments, push notifications and any screen with a form.
4. Week 4: Release in stages. Use a staged rollout in Play Console and watch crash reports before going to 100%.

A simple app with up to date libraries can move faster. An app that has not been touched for two years usually needs the full plan.

Common mistakes

• Changing the target number without testing on an Android 16 device.
• Updating the app but leaving old SDKs that still crash on new devices.
• Waiting until an urgent bug appears before starting the upgrade.
• Forgetting that the same rule comes back every year, usually in August.

If you also have a developer account to verify before 2027, our guide on Android developer verification for businesses with their own apps covers that separate deadline.

Where Ascent24 fits

Ascent24 maintains and upgrades business apps. We can audit your app, move it to API 36, fix the layout and navigation issues, test on real devices and release it through your Play Console. If you do not have the original developer any more, we can start from your code repository.

FAQs

What is the Google Play target API level for 2026?

From 31 August 2026, new apps and app 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.

Can I still get an extension?

Google offered an extension to 1 November 2026 through a form in Play Console. That date has passed, so the practical step now is to update the app.

Will my app be removed from Google Play?

Google's page does not say the app is removed. If it targets Android 14 or lower, it is only shown to devices running that Android version or lower, so new users on newer phones will not find it.

Why can't I publish a small bug fix?

Every app update counts as a submission, and submissions must target API 36. The rule applies to small fixes as well as big releases.

How long does an API 36 upgrade take?

It depends on the app's age and libraries. A well maintained app may take days. An older app often needs two to four weeks including testing on real devices.

Sources

• Google Play Console Help, "Target API level requirements for Google Play apps": https://support.google.com/googleplay/android-developer/answer/11926878
• Android Developers, "Behavior changes: Apps targeting Android 16 or higher": https://developer.android.com/about/versions/16/behavior-changes-16