Google Play's 1 November deadline just passed: is your app still updatable?

The short answer

Since 31 August 2026, Google Play has accepted new apps and app updates only if they target Android 16 (API level 36). Developers who asked for more time got an extension, and that extension ran out on Sunday 1 November (Android Developers, target API level requirements, last updated 16 October 2026).

If your Android app still targets an older API level, it keeps working for people who already have it, but you can’t ship your next update. If it targets API 34 or lower, it also stops showing up for new users on newer phones.

This page explains how to check your app in ten minutes, why the fix is rarely a one-line change, and how to decide between patching, upgrading and rebuilding.

What changed on 1 November 2026

1 November 2026 was the last day of the extension Google offered on its Android 16 (API 36) target requirement. From now on, an Android app that targets an API level below 36 can’t publish updates on Google Play. An app that targets API 34 or lower is also hidden from new users on devices running newer Android versions.

Google Play’s target API rule has two parts (Google Play Console Help, target API level requirements):

Your app targets	Existing users	New users on newer Android phones	Publishing updates
API 36 (Android 16) or higher	Unaffected	Can find and install it	Allowed
API 35 (Android 15)	Unaffected	Can find and install it	Blocked until you target 36
API 34 (Android 14) or lower	Unaffected: they can still use and reinstall it	Can’t find or install it	Blocked until you target 36

The table covers ordinary phone and tablet apps. Google sets lower targets for Wear OS and Android Automotive OS apps (API 35) and for Android TV and Android XR apps (API 34). Permanently private apps distributed only inside one organisation are exempt (Android Developers).

So nothing visibly broke on Sunday. The damage shows up later: when you need to fix a payment bug, change a price screen or comply with a new rule, and Play Console won’t accept the build.

How to check your app in ten minutes

Look for a target API warning in Play Console, then confirm the targetSdkVersion in your app’s Android build file. If the number is below 36, your next update will be rejected until it’s raised.

1. Open Play Console and read your notifications and policy status. Google says affected apps were sent notices and that the extension form was reached from the policy warning’s details page (Google Play Console Help). A warning there is your answer.
2. Find the target number in the code. In a native Android or Flutter project, it lives in the app-level Gradle file (android/app/build.gradle or build.gradle.kts) as targetSdk or targetSdkVersion. In Flutter it may read flutter.targetSdkVersion, which means the value comes from your Flutter version. In an Expo project it’s set by the Expo SDK version and the app config.
3. Write down three more facts: the framework version (Flutter, React Native/Expo or native), the date of the last release, and who holds the source code and the Play Console owner login.

If you can’t do step 2 or step 3 because the code or the login sits with a former developer, that’s your real problem, and it comes before any API level. We wrote about that gap in what it costs when your agency and developers are different companies.

Why raising the number is the easy part

Changing the target to 36 is one line of code. The work is testing and fixing the behaviour changes Android 16 switches on for apps that target it, especially on tablets and foldables.

Google’s Android 16 behaviour changes page lists what changes the moment you target API 36. The changes most likely to affect a typical Indian SMB app:

• Large screens. On displays at least 600dp wide (most tablets and unfolded foldables), Android ignores orientation, resizability and aspect-ratio locks. An app designed only for portrait phones will be stretched across the full screen. Google notes there is a temporary opt-out, which won’t apply once apps target API 37.
• Edge-to-edge is mandatory. Apps can no longer opt out, so headers, buttons and bottom bars can slide under the status or navigation bar if the layout wasn’t built for it.
• Back button behaviour. Predictive back animations are on by default, and the old onBackPressed callback is no longer called. Any screen that used it to show “Are you sure you want to exit?” or save a form needs rework.
• Indian-language text. The elegantTextHeight setting is ignored, and Google specifically says to check layouts that use Telugu, Tamil, Kannada, Malayalam, Gujarati or Odia text for rendering changes. If your app serves customers in Telugu, test those screens.

None of these is hard on its own. Together, they mean a proper test pass on a phone, a tablet and ideally a foldable before you ship. Secondary migration guides make the same point: the target bump is quick, and the large-screen changes are where the time goes (AppsOnAir, Android 16 target SDK guide).

Flutter and React Native apps: the upgrade hiding behind the deadline

If your app was built with Flutter or React Native and hasn’t been touched since 2023 or 2024, reaching API 36 usually means upgrading the framework and its plugins first, not just editing the target number.

A newer target API generally needs newer Android build tooling, which needs newer framework and plugin versions. The further behind the app is, the more of that chain moves at once. Two recent framework changes add to the work:

• Flutter. Flutter 3.44 and Dart 3.12, released at Google I/O in May 2026, made Swift Package Manager the default for iOS and macOS (Flutter blog, What’s new in Flutter 3.44). An older Flutter app that you upgrade for Android will often need its iOS dependency setup revisited too.
• React Native on Expo. Expo SDK 55 supports only React Native’s New Architecture, and SDK 54 was the last release with the old one (Expo changelog, SDK 55). Moving an older Expo app onto current SDKs means every native library it uses must work with the New Architecture, or be replaced.

This is the point where a “small Play Store fix” turns into a project. It’s better to find out in the first hour than in the second week.

Your iOS app has its own build rule

Since 28 April 2026, every app uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK. An iOS app built with older tools can’t ship updates either.

Apple lists this under its upcoming requirements. It’s a build requirement, not a device requirement, so your app can still support older iPhones. But if your Android upgrade forces a framework upgrade, plan the iOS rebuild in the same piece of work. Doing them separately means testing the same app twice.

What’s next: Android developer verification (not in India yet)

Google’s new developer verification rules for apps installed outside the Play Store started on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand. India isn’t in that first phase, and no India date has been announced.

According to Android Authority and Techenclave, Google plans to expand the rules globally in 2027. This matters if your business shares APK files directly with field-sales staff, distributors or delivery partners instead of using Play. Once the rules reach India, apps from unverified developers will be harder to install on certified Android phones. If you distribute that way, find out now who the “developer” of record is for each app, and watch Android Developers for an India date.

While you’re in Play Console: fix your store listing

Google Play lets you create up to 50 custom store listings, each tailored by country, user state or search keyword. An upgrade release is a good time to update your listing as well.

Google’s custom store listings page says Play Console can suggest keywords and deploy a listing tailored by Gemini for those searches, and that a listing can be shown through its own URL. For an Indian SMB, practical uses include:

• a listing for Telangana and Andhra Pradesh users with Telugu screenshots
• a listing for the exact search term customers use for your category
• a separate listing for people who already know you and are returning

Your screenshots also need checking. If the upgrade changed how the app looks on tablets or edge-to-edge, update them so the listing matches what people install. On the Apple side, keywords can be assigned to individual Custom Product Pages, a change Apple introduced in 2025 (Apple WWDC25, session 328).

Patch, upgrade or rebuild? A decision table

Patch if the app’s framework is recent and you control the code. Upgrade if the code is sound but the framework and plugins are a year or two behind. Rebuild only if you can’t access the source, the dependencies are abandoned, or the app no longer fits how your business works.

Situation	Patch	Upgrade	Rebuild
Framework and plugin versions	Recent and maintained	One to two years behind; most plugins still maintained	Key plugins abandoned or no supported path forward
Source code and Play Console access	You have both	You have both	Code is missing, incomplete, or held by someone who won’t hand it over
Tests and documentation	Some exist	Few or none	None, and the original developer is unreachable
Fit with current business	Still fits	Still fits, with minor changes	Your process, pricing or customers have changed a lot
Typical work	Raise target to 36, fix behaviour changes, test, release	Framework and plugin upgrade, iOS rebuild with Xcode 26, full test pass	New build, data migration, store listing transfer

If you’re not sure which column you’re in, that’s normal. Most owners we speak to only know which developer built the app, not which framework version it runs on.

Find out where your app stands

Send us a screenshot of your Play Console warning, your app’s name and, if you have it, the repository link through the contact page. Someone on our build team will read it and reply with a scoped recommendation: patch, upgrade or rebuild, and what each would involve for your app. No timeline promises until we’ve seen the code.

If you’d like to see how we work on apps first, read about app maintenance and upgrades.