Short answer: since August 31, 2026, every new app and every app update on Google Play must target Android 16 (API level 36) or higher. Existing apps that target lower than Android 15 (API 35) stop showing to new users on newer Android versions. In a Flutter app, you usually fix this by upgrading Flutter (3.35 already targets API 36 by default), checking targetSdk and compileSdk in android/app/build.gradle, updating the Android Gradle Plugin, and testing the Android 16 behaviour changes before you upload.
Google raises this requirement every year, and it’s one of the most common reasons a Flutter app suddenly can’t be updated. Here’s what the rule says, and the exact steps I follow to move a Flutter app to the new target.
What Google Play requires right now
From Google’s target API level requirements page:
| Who | Requirement | Since |
|---|---|---|
| New apps and app updates (phones and tablets) | Target Android 16 (API 36) or higher | 31 Aug 2026 |
| Existing apps, to stay visible to new users on newer devices | Target Android 15 (API 35) or higher | 31 Aug 2026 |
| Wear OS and Android Automotive OS (new apps and updates) | Android 15 (API 35) or higher | 31 Aug 2026 |
| Android TV and Android XR | Android 14 (API 34) or higher | See Google’s table |
Google offered an extension to 1 November 2026 for apps that needed more time, through a form linked from the policy warning in Play Console. That date has passed, so if your app is still behind, the update is no longer optional.
The only exception Google lists is permanently private apps, meaning apps restricted to users in one organisation for internal use.
What happens if you don’t update
- You can’t upload a new version. Play Console rejects any app bundle that targets a lower API level. Even an urgent bug fix is blocked until you update the target.
- New users on newer phones can’t find the app. If your app targets below API 35, it stops being available to new users whose devices run a newer Android version than your target.
- Current users keep the app. Google says people who already installed the app aren’t affected. But you can’t ship them fixes, and your audience slowly shrinks.
Play Console shows a warning on the Policy status page and in your inbox before this happens. If you see one, plan the update for that week, not for the deadline.
How to update a Flutter app to target API 36
1. Check where you are
Open android/app/build.gradle (or build.gradle.kts) and look at the defaultConfig block:
android {
compileSdk = flutter.compileSdkVersion
defaultConfig {
minSdk = flutter.minSdkVersion
targetSdk = flutter.targetSdkVersion
// ...
}
}
If it says flutter.targetSdkVersion, the target comes from your Flutter version. If it says a number like 34 or 35, someone hard-coded it, and you need to change it yourself.
2. Upgrade Flutter
In Flutter 3.35, flutter.compileSdkVersion and flutter.targetSdkVersion are both 36, and flutter.minSdkVersion is 24. Older Flutter versions use older defaults. Upgrade on a separate branch:
flutter upgrade
flutter pub upgrade --major-versions
dart fix --apply
Then read the breaking changes for every major package update. The free Flutter package checker shows which packages are discontinued or several major versions behind before you start.
3. Set the SDK levels
Either keep the Flutter defaults, or set them explicitly:
android {
compileSdk = 36
defaultConfig {
targetSdk = 36
}
}
Plugins sometimes need compileSdk at least as high as the target, so keep both at 36.
4. Update the Android build tools
A new compileSdk usually needs a newer Android Gradle Plugin (in android/settings.gradle) and Gradle wrapper (in android/gradle/wrapper/gradle-wrapper.properties), and sometimes a newer Kotlin version. If the build fails with a message about an unsupported compile SDK or AGP version, that’s what it means. Android Studio’s AGP Upgrade Assistant can make these changes for you.
5. Test the Android 16 behaviour changes
Targeting a new API level turns on that version’s behaviour changes. Android’s Android 16 behaviour changes page lists them. The ones I check first in Flutter apps:
- Edge-to-edge. Apps targeting Android 16 can no longer opt out of edge-to-edge display. Check that app bars, bottom navigation and buttons aren’t hidden under the status bar or gesture bar. Wrapping screens in
SafeArea, or usingMediaQuery.paddingOf(context), fixes most issues. - Large screens. On tablets and foldables, Android 16 ignores many orientation and resizability restrictions for apps targeting API 36. If your app is locked to portrait, test it on a tablet emulator in landscape.
- Back navigation. Test the system back gesture on every screen, especially screens with
PopScopeor custom back handling. - Permissions and background work. Re-test location, notifications, camera and anything running in the background on an Android 16 emulator.
6. Build, test and upload
flutter build appbundle --release
Install the release build on a real device or an Android 16 emulator, go through the main flows, then upload the .aab to an internal or closed testing track before production. The full release checklist is in how to publish a Flutter app to the App Store and Google Play.
From my own work: I’ve had to ship a hotfix while a target SDK update was blocking uploads. That’s exactly the situation to avoid. Now I move every app I maintain to the new target soon after Google announces it, on a branch, with a test build the same week. The yearly routine is in the Flutter app maintenance checklist.
How long does it take?
For a well-maintained Flutter app on a recent Flutter version, often a few hours: bump the version, run the build, test the behaviour changes. For an app that’s two or three Flutter versions behind, with discontinued packages and old Gradle files, it can take several days, because the target SDK update pulls every other overdue upgrade with it. That’s why updating a little every quarter is cheaper than updating everything once a year.
Frequently asked questions
What target API level does Google Play require in 2026?
New apps and app updates must target Android 16 (API level 36) or higher since August 31, 2026. Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer devices. Wear OS and Android Automotive OS apps need API 35, and Android TV and Android XR apps need API 34.
How do I change the target SDK in a Flutter app?
Open android/app/build.gradle (or build.gradle.kts) and set targetSdk in defaultConfig, along with compileSdk. If it uses flutter.targetSdkVersion, upgrading Flutter updates it for you: Flutter 3.35 targets API 36 by default. Then update the Android Gradle Plugin if the build asks for it.
Will my existing users lose the app if I don't update?
No. Users who already installed the app keep it. But you can’t upload updates, including bug fixes, and if your target is below API 35 the app stops being available to new users on newer Android versions.
Can I still get an extension?
Google offered an extension to November 1, 2026 through a form linked from the policy warning in Play Console. That date has passed, so plan to update now. Check the Policy status page in Play Console for the current state of your app.
Does raising the target SDK break anything in Flutter?
It can. Each Android version brings behaviour changes that only apply once you target it. For Android 16 the main ones are enforced edge-to-edge display, fewer orientation and resizability restrictions on large screens, and back navigation changes. Test these on an Android 16 emulator before you upload.
Is a target API warning blocking your app? Send me the details. I’m Muhammad Naeem, a Flutter developer who maintains live apps on both stores, and I can usually move an app to the new target within a few days. See also app maintenance and support.
Need a Flutter app built? Tell me about your project, or see case studies of apps I’ve worked on.
