Originally published on AppRanker.
Google Play has refused app updates below target API 36 since the one-time extension ended on November 1, 2026 — and bumping targetSdk is the easy part. Target Android 16 and three production behaviors change: layouts draw under the system bars, the back button stops calling onBackPressed(), and tablets drop your portrait lock. Nothing fails a build — the bugs arrive later, as screenshots and one-star reviews.
What Play enforces now
| Rule | Date | What it means |
|---|---|---|
| New apps and updates must target Android 16 (API 36) or higher | Aug 31, 2026 | A release below targetSdk 36 is rejected |
| One-time extension requested in Play Console | Ended Nov 1, 2026 | Extra time, never a renewal |
| Existing apps must target API 35 or higher | Ongoing | Below that, new users on newer Android can't install |
| Wear OS / Android Automotive OS | Aug 31, 2026 | API 35 is enough |
| Android TV / Android XR | Aug 31, 2026 | API 34 is enough |
Permanently private, org-internal apps are exempt.
The requirement gates releases, not listings: an app targeting 35 stays installable, it just cannot receive updates. Confirm your live number first: Play Console's App bundle explorer shows each bundle's target SDK, or locally:
aapt2 dump badging app-release.apk | grep -o "targetSdkVersion:'[0-9]*'"
Flutter 3.38+ already targets 36 by default, and the React Native template does from 0.81 — teams often hit the changes below right after a routine framework upgrade.
Edge-to-edge: content lands under the system bars
For targetSdk 36 apps, android:windowOptOutEdgeToEdgeEnforcement is ignored on Android 16: the app draws behind the status and navigation bars, and anything unpadded gets covered. Developers report the ActionBar shifted down, bottom sheets gaining padding in landscape, and adjustPan forms stacking at the top when the keyboard opens.
In Views:
- Delete
windowOptOutEdgeToEdgeEnforcementfrom every theme — it no longer protects you on Android 16 and hides the problem on Android 15 test devices. - Call
enableEdgeToEdge()per activity, drop the deprecatedsetStatusBarColor(), and pad content with system bar plus display cutout insets:
ViewCompat.setOnApplyWindowInsetsListener(binding.root) { view, insets ->
val bars = insets.getInsets(
WindowInsetsCompat.Type.systemBars() or WindowInsetsCompat.Type.displayCutout()
)
view.updatePadding(bars.left, bars.top, bars.right, bars.bottom)
WindowInsetsCompat.CONSUMED
}
- On screens with text fields, use
WindowInsetsCompat.Type.ime()rather thanadjustPanoradjustResize; for light backgrounds setWindowCompat.getInsetsController(window, window.decorView).isAppearanceLightStatusBars = true.
Compose: pass the Scaffold content padding down, or use Modifier.safeDrawingPadding() / Modifier.imePadding(). Flutter: wrap screens in SafeArea or read MediaQuery.paddingOf(context) — Flutter warns the Android 16 opt-out can crash. React Native: replace <SafeAreaView> with react-native-safe-area-context; StatusBar's backgroundColor and translucent change, and 0.81's edgeToEdgeEnabled Gradle property matches older Android.
Predictive back: onBackPressed() goes silent
Predictive back is on by default for targetSdk 36 apps: onBackPressed() is never called and KEYCODE_BACK never dispatched, so custom back logic silently stops running. The classic victim is a WebView wrapper that overrode onBackPressed() to call webView.goBack() — back now exits the app instead of going back one page.
Move the logic to OnBackPressedCallback (AndroidX Activity 1.6.0+), enabled only while your app needs to intercept back, so the system animation plays the rest of the time. For a WebView, tie it to page history:
class BrowserActivity : AppCompatActivity() {
private val webBack = object : OnBackPressedCallback(false) {
override fun handleOnBackPressed() { webView.goBack() }
}
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
onBackPressedDispatcher.addCallback(this, webBack)
webView.webViewClient = object : WebViewClient() {
override fun doUpdateVisitedHistory(view: WebView, url: String?, isReload: Boolean) {
webBack.isEnabled = view.canGoBack()
}
}
}
}
With no history, the callback is disabled and back leaves the screen with the system animation.
- Compose:
BackHandler(enabled = ...), orPredictiveBackHandlerto animate with the gesture. - Flutter:
PopScopewithonPopInvokedWithResultreplaces the deprecatedWillPopScope; predictive back transitions are on by default inMaterialAppsince 3.38. - React Native:
BackHandlerstill works in 0.81, but native modules overridingonBackPressed()must move toOnBackPressedDispatcher.
If you cannot finish in time, android:enableOnBackInvokedCallback="false" on the <application> or a single <activity> is a documented temporary opt-out — a stopgap, not a fix.
Tablets and foldables ignore your orientation lock
On displays with a smallest width of 600dp or more, Android 16 ignores android:screenOrientation, resizeableActivity="false", the min/max aspect ratio attributes and setRequestedOrientation() for targetSdk 36 apps: a portrait-only app stretches to fill a landscape tablet or an open foldable instead of being letterboxed. Phones are unaffected — the change applies only at 600dp and up. Games are exempt via android:appCategory, and users can pick the app's default in the device's aspect ratio settings.
A temporary opt-out exists (android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY set to true), but Google's Android 17 notes say it disappears for apps targeting API 37. The lasting fix is making main screens survive rotation and resizing:
- Keep screen state in a
ViewModelor saved state so rotation does not reset a form, a video or a canvas. - Test on Pixel Tablet and Pixel Fold emulator images in both orientations, and drag the window in multi-window mode.
- Cap the width of text-heavy layouts so lines do not run across a 12-inch screen.
- Check camera previews first — they look stretched or sideways most often.
Smaller changes that still bite
-
elegantTextHeightis ignored. Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu and Thai text can render with different line heights — check for clipped text. -
Fixed-rate tasks catch up only once.
ScheduledExecutorService.scheduleAtFixedRate()runs at most one missed execution when the app returns to a valid lifecycle state. -
Heart rate permissions are more granular. Use
READ_HEART_RATE(in use) orREAD_HEALTH_DATA_IN_BACKGROUND, notBODY_SENSORS(_BACKGROUND). -
MediaStore.getVersion()is unique per app. Do not parse it or compare it across apps. -
Bluetooth bond loss now raises
ACTION_KEY_MISSINGandACTION_ENCRYPTION_CHANGEbroadcasts.
Plan one more deadline while in the build files: from February 1, 2027, Play blocks updates to apps targeting Android 15+ without 16 KB page support on 64-bit devices. Verify native libraries with zipalign -c -P 16 -v 4 app-release.apk or APK Analyzer's Alignment column.
Key takeaways
- Bump
targetSdkto 36 first, then fix the three breaking behaviors: insets, back and large screens. - Remove the edge-to-edge opt-out and pad with system bar + cutout insets; handle the keyboard with IME insets, not
adjustPan. - Move all custom back logic off
onBackPressed()/KEYCODE_BACKontoOnBackPressedCallback,BackHandlerorPopScope. - Portrait locks still work below 600dp — test tablets and foldables in both orientations.
- One grep before you bump:
windowOptOutEdgeToEdgeEnforcement|onBackPressed|KEYCODE_BACK|screenOrientation|resizeableActivity|AspectRatio|elegantTextHeight|WillPopScope.
Ship with a staged rollout, watch crash and ANR rates in Android vitals, and retake screenshots if the edge-to-edge layout changed the look of your app. The full target API 36 migration guide has the complete five-section checklist and an FAQ for the edge cases; check the AppRanker board to see what a paid rank costs for your app today.
Which of these hit you first after the bump — edge-to-edge padding, a back button that closed the app, or the stretched tablet layout — and how did you catch it before your users did?
Top comments (2)
Useful checklist, thanks. The predictive-back WebView example is the one I'd have missed. My own app, HelperBook, is built with Compose and targets API 35 today, so its next update is the bump to 36. For Compose screens, does Scaffold padding cover most of the edge-to-edge work in your experience, or do dialogs and bottom sheets still need their own insets handling? And did the large-screen orientation change catch anyone with a camera-capture screen?
One thing worth adding to the edge-to-edge checklist: test with 3-button navigation as well as gesture navigation. Layouts that look fine with gestures often get covered by the button bar, and the insets behave differently between the two.