Flutter Target API 36 for Google Play: Deadline and Fix

Since August 31, 2026, Google Play refuses new apps and app updates that target below Android 16 (API level 36). The extension Google offers apps that need more time runs only to November 1, 2026. Flutter 3.35 and later target API 36 by default, so for most Flutter apps the fix is a toolchain upgrade and a rebuild, plus a check of three Android 16 behavior changes. Not a rewrite.

The dates

Sources: Google's target API level requirements and 16 KB page size guide, checked October 2, 2026.

Which Flutter version targets API 36

A Flutter app inherits its Android SDK levels from the Flutter toolchain unless the project overrides them. These are the defaults in Flutter's own Gradle plugin (FlutterExtension.kt) at each release tag:

So any Flutter release from 3.35 on produces an API 36 app, as long as your project still points at Flutter's value. Projects created by flutter create do, in android/app/build.gradle or build.gradle.kts:

defaultConfig {
    minSdk = flutter.minSdkVersion
    targetSdk = flutter.targetSdkVersion
}

If someone replaced that line with a number, such as targetSdk = 34, the toolchain upgrade changes nothing: set it to 36 (or back to flutter.targetSdkVersion). The same goes for compileSdk, which must be at least the target. If a plugin then fails with “compile against version 36 or later”, see the compileSdk 36 error, explained.

Check what a built app actually targets

Don't trust the Gradle file alone; read the value from the artifact you are about to upload. For an Android App Bundle:

bundletool dump manifest --bundle=app-release.aab \
  --xpath=/manifest/uses-sdk/@android:targetSdkVersion

For an APK, with the Android SDK build tools:

aapt2 dump badging app-release.apk | grep targetSdkVersion

Both should print 36. Checking before you upload saves a rejected release.

What changes when your app targets API 36

Targeting a new API level opts your app into that release's behavior changes. Google's Android 16 behavior changes list three that Flutter apps meet most often:

• Edge-to-edge is no longer optional. The windowOptOutEdgeToEdgeEnforcement opt-out is disabled, so your UI draws behind the status and navigation bars. Screens that wrap their content in SafeArea (or read MediaQuery.paddingOf) are fine; check the ones that don't, especially custom app bars and bottom buttons.
• Predictive back is on by default. On Android 16 devices, onBackPressed is no longer called. In Flutter, intercept Back with PopScope; the older WillPopScope is deprecated. Native plugin code that overrides onBackPressed needs the same update, or the temporary android:enableOnBackInvokedCallback="false" opt-out.
• Orientation locks are ignored on large screens. On displays whose smallest width is 600dp or more (tablets, unfolded foldables), Android ignores screenOrientation, resizability and aspect-ratio limits. A portrait-only layout will be shown in landscape there. Google offers a temporary opt-out that stops working at API 37.

Keep your upload key

Play accepts an update only if it keeps the same application ID and is signed with your app's upload key. Before you rebuild anywhere new, find the keystore (and its passwords) that signed your last release. If it is lost and the app uses Play App Signing, request an upload key reset in Play Console first. An update signed with a new key is accepted only after Google processes that request.

Rebuild without upgrading your own machine

If your laptop is pinned to an old Flutter for another project, or you never had the Android toolchain installed, you can compile in the cloud. Code2Native's default Flutter toolchain is 3.44.5 with Android platform 36 and NDK 28.2, so a project that uses flutter.targetSdkVersion comes out at API 36:

1. Upload the project as a ZIP, or give a Git URL. Leave out build/, caches and secrets.
2. Choose an AAB for Google Play, and upload the keystore that holds your upload key so the bundle is signed with it.
3. Read the real Gradle log while it builds. If it fails, the build page says which step failed and why.
4. Run the bundletool check above on the download, then upload it to Play Console.

One caveat: to compile older projects, the builder can pick Flutter 3.24.5 or 3.19.6, whose defaults target below API 36. It does so when the SDK constraint in pubspec.yaml only allows an older Dart, when intl is pinned below 0.20 together with flutter_localizations, when carousel_slider is below 5 or syncfusion_flutter_pdfviewer below 26, or when android/ still applies the Flutter Gradle plugin the pre-3.16 way. The [c2n] Toolchain line in the build log names the version and the reason. That output is fine for APKs you share directly, but Play refuses it as an update: update those pins, or move android/ to the Flutter Gradle plugins block, first. See building an old Flutter app in the cloud.

Source compiles need Builder ($39/month, up to 20 Android source compiles a month, using included credits) or Pro ($99/month). Check which projects are supported before you buy, and see pricing for what each plan includes. A successful build is not a Play approval: if this is a new personal developer account, Google's closed-testing requirement still applies.

While you are rebuilding: 16 KB pages

From February 1, 2027, Play requires 16 KB memory page support for updates to apps that target Android 15 or higher and ship native code. Every Flutter app ships native code (the Flutter engine and your compiled Dart), so the rule applies to yours. Build with a current Flutter release and check the result instead of assuming: prebuilt .so files inside older plugins are the usual exceptions. Google's guide documents this check of an APK's zip alignment:

zipalign -c -P 16 -v 4 app-release.apk