Play Console will not accept the release because of its target API level
Play Console blocks submitting a release whose app bundle targets an API level below 36Short answer
Since 31 August 2026, Google Play accepts new phone and tablet apps and updates only if they target Android 16 (API level 36); the extension window ran to 1 November 2026. In a Flutter app, set targetSdk to 36 (flutter.targetSdkVersion on current stable), rebuild the bundle, then test edge-to-edge layouts, back navigation and tablet orientation, which change at that level.
Fix it fast
1Find out which cause you have
Read the target level from the file you are about to upload, not from the Gradle file you think applies. Build the release, then let aapt2 from the SDK build-tools print the manifest values Play will see.
flutter build apk --release AAPT2="$(ls -d "$ANDROID_HOME"/build-tools/* | tail -n 1)/aapt2" "$AAPT2" dump badging build/app/outputs/flutter-apk/app-release.apk | grep -E "sdkVersion|targetSdkVersion"2Match what you see, then jump to its fix
- 1
aapt2 prints targetSdkVersion:'35' or lower, and android/app/build.gradle(.kts) contains a literal numbertargetSdk is typed as a fixed number in the app moduleFix - 2
targetSdk uses flutter.targetSdkVersion but the built app still reports a lower level, or Gradle says the maximum recommended compile SDK for your AGP is lowerThe Flutter SDK or Android Gradle Plugin is too old for API 36Fix - 3
Headers sit under the clock, bottom buttons hide behind the gesture bar on Android 15 and 16After the bump, content slides under the status and navigation barsFix - 4
A 'discard changes?' prompt never appears, or the app closes when it should go back one screenBack navigation behaves differently on Android 16Fix - 5
On large screens the app rotates or fills the whole window although it is locked to portraitPortrait-only layouts stretch on tablets and foldablesFix
- 1
What does the error look like?
Play Console blocks submitting a release whose app bundle targets an API level below 36A target API level warning on the Policy status page, with an extension form linkUsers on newer phones see that the app is not available because it was made for an older version of Android
Cause 1 of 5
targetSdk is typed as a fixed number in the app module
1Check
The deadline for the rule (checked against Google's Play requirement pages on 16 November 2026): new apps and updates must target API 36 from 31 August 2026; Wear OS and Automotive need 35, Android TV and XR need 34. Existing apps must target at least 35 to keep reaching new users on newer Android. A number written in by hand never moves when you upgrade Flutter, so the app quietly falls behind.
grep -n -E "targetSdk|compileSdk" android/app/build.gradle*2Fix
Go back to Flutter's value or write 36. compileSdk has to be at least as high as targetSdk, so raise both together.
// android/app/build.gradle.kts
android {
compileSdk = flutter.compileSdkVersion // or 36
defaultConfig {
targetSdk = flutter.targetSdkVersion // or 36
}
}3Verify
Rebuild and read the manifest again; then upload to an internal testing track before production.
flutter build appbundle --release
flutter build apk --release && "$AAPT2" dump badging build/app/outputs/flutter-apk/app-release.apk | grep targetSdkVersionCause 2 of 5
The Flutter SDK or Android Gradle Plugin is too old for API 36
1Check
flutter.targetSdkVersion is whatever your Flutter SDK defines, so an old Flutter keeps an old target. Current stable (3.50) resolves it to 36. If you write 36 yourself, the Android Gradle Plugin must know that level: Android lists AGP 8.9.1 as the minimum for API 36.
flutter --version
grep -n "com.android.application" android/settings.gradle*2Fix
Upgrade Flutter and let its migrators run, then raise AGP and the Gradle wrapper to a matching pair if the build asks for it. If you cannot upgrade Flutter before the deadline, set 36 explicitly and raise AGP alone.
flutter upgrade
flutter clean && flutter pub get
flutter build appbundle --release3Verify
The bundle builds without compile SDK warnings and aapt2 reports targetSdkVersion:'36'.
flutter build apk --release && "$AAPT2" dump badging build/app/outputs/flutter-apk/app-release.apk | grep targetSdkVersionCause 3 of 5
After the bump, content slides under the status and navigation bars
1Check
Apps that target 35 already draw edge to edge, but could opt out with windowOptOutEdgeToEdgeEnforcement. When you target 36 on an Android 16 device that attribute is ignored. Look for it in your theme files, and for screens that do not reserve room for system bars.
grep -rn "windowOptOutEdgeToEdgeEnforcement" android/app/src/main/res/
grep -rn "SafeArea\|viewPadding" lib/ | head -n 202Fix
Remove the opt-out and let each screen handle insets: wrap top-level bodies in SafeArea, or read MediaQuery padding where a design needs colour behind the bars.
Scaffold(
body: SafeArea(
child: content,
),
)3Verify
Run on an Android 16 emulator with gesture navigation and with three-button navigation, in light and dark themes.
flutter run --release -d emulator-5554Cause 4 of 5
Back navigation behaves differently on Android 16
1Check
For apps that target 36 running on Android 16, predictive back is on by default, onBackPressed is no longer called and the back key event is not sent. Flutter code built on the deprecated WillPopScope, or native code that overrides onBackPressed in MainActivity or a plugin, stops working.
grep -rn "WillPopScope" lib/
grep -rn "onBackPressed" android/app/src/2Fix
Move to PopScope: decide up front with canPop whether a route may close, and react in onPopInvokedWithResult. As a short-term measure only, Android lets you opt out with android:enableOnBackInvokedCallback="false" on the application tag.
PopScope(
canPop: !hasUnsavedChanges,
onPopInvokedWithResult: (didPop, result) async {
if (didPop) return;
final discard = await confirmDiscard(context);
if (discard && context.mounted) Navigator.of(context).pop();
},
child: form,
)3Verify
On an Android 16 emulator, swipe back from every screen that guards unsaved data and from the home screen.
flutter run -d emulator-5554Cause 5 of 5
Portrait-only layouts stretch on tablets and foldables
1Check
Targeting 36 makes Android ignore orientation, resizability and aspect-ratio limits on displays at least 600dp wide (games excepted). That covers android:screenOrientation in the manifest and orientation requests made from Flutter. Phones are not affected.
grep -n "screenOrientation\|resizeableActivity" android/app/src/main/AndroidManifest.xml
grep -rn "setPreferredOrientations" lib/2Fix
Make the main screens usable in landscape with LayoutBuilder or breakpoints. Android offers a temporary per-app opt-out property, but it stops applying once you target API 37.
<!-- AndroidManifest.xml, inside <application>; temporary -->
<property
android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY"
android:value="true" />3Verify
Test on a tablet or foldable emulator in both orientations and in split screen.
flutter emulatorsHow do I stop it coming back?
- Keep targetSdk on flutter.targetSdkVersion and upgrade Flutter at least twice a year, so the target moves with the SDK.
- Plan the bump each spring: Play's recent deadlines have fallen on 31 August, and any extension has to be requested through Play Console before it runs out.
- Read the behaviour-change list for each new Android version and keep one emulator on the newest release in your test routine.
- Ship target bumps through an internal or closed testing track first, so layout and back-navigation regressions surface before users see them.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Related fixes
Mobile apps
Flutter Android build stops with Execution failed for task ':app:…'
Execution failed for task ':app:compileFlutterBuildRelease'.
The line only tells you which Gradle step broke; the task name in the quotes tells you why.
5 causes, each with a fixMobile apps
Google Play says the app does not support 16 KB memory pages
check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a
Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.
5 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fix