◉RORK LABJP
●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30
Articles/Dev Tools
⬡ Dev Tools/2026-08-23Advanced

Predictive back on Android 16: after targetSdk 36, migrate now or keep the opt-out?

Targeting API 36 turns predictive back on by default and stops onBackPressed from firing. Expo already opts you out by default, so here is how to find the apps that drifted from that default, and how to keep the opt-out from vanishing on the next prebuild.

Android 164predictive backExpo237React Native243config plugin6

✦ Premium Article

After bumping targetSdkVersion to 36, the preview screen looked different when I swiped in from the edge. The screen shrank slightly and revealed what was behind it. That is Android's predictive back animation.

That part I expected. What stopped me was what came next. A swipe I meant as "go back to the grid" was being treated as "leave the app."

The React Native announcement says BackHandler keeps working. And it did keep working. Yet the outcome of the back gesture had changed. It took me a while to understand how both can be true — and, more embarrassingly, why an Expo project should not have behaved this way in the first place.

The Google Play deadline for targeting API level 36 (August 31, 2026, or November 1 if you requested an extension) is behind us. If you are still shipping updates, your app almost certainly targets 36 now. This piece is about the decision that is left: when, and how far, to go with real predictive back support. Everything below was checked against the official docs as of November 2026, with Expo SDK 58 as the current release.

"BackHandler still works" and "back navigation is unchanged" are different claims

Apps targeting Android 16 get predictive back enabled by default. Two things change at the OS level.

Before (targetSdk 35 and below)targetSdk 36 on Android 16+ devices
onBackPressed() is calledNot called
KeyEvent.KEYCODE_BACK is dispatchedNot dispatched

React Native 0.81 absorbed that change so the JS-side BackHandler keeps firing. The community announcement states that onBackPressed is no longer called, that BackHandler should continue to work, and that custom native back handling may need a manual move to OnBackPressedDispatcher.

What I misread was the scope of "BackHandler still works." What keeps working is the handler you registered yourself on hardwareBackPress. Screens where you registered nothing — the ones that leave back navigation to your navigation library — are not covered by that promise.

React Navigation 7.x does not support predictive back yet. Its getting started guide says you need to disable it for the system back gesture to work properly, and shows android:enableOnBackInvokedCallback="false". On the Expo side there are reports of stack back navigation breaking under predictive back, and real support is being built into the newer native stack in react-native-screens.

So the thing that breaks is not the BackHandler you wrote. It is the code you never wrote, which is why rereading your own source gives you no reason for the failure.

Expo already opts you out by default

What I realized only after digging was that the first document I should have read was Expo's app config reference, not Android's behavior changes page.

In the SDK 54 release notes, Expo disabled predictive back by default in all projects and made it opt-in through android.predictiveBackGestureEnabled in app.json. The current app config reference for SDK 58 still lists the default as false.

I also read the plugin itself. The PredictiveBackGesture module in @expo/config-plugins writes android:enableOnBackInvokedCallback onto the <application> element on every prebuild. The value is "true" only when predictiveBackGestureEnabled is true; anything else becomes "false". It never touches <activity>.

That gives you three conclusions:

  • An Expo (CNG) project with no setting at all keeps the old back behavior, even at targetSdk 36.
  • If back navigation changed, some setting has drifted from that default.
  • There are only three places to look: predictiveBackGestureEnabled: true in app.json, a hand-managed manifest under android/, or a leftover value on an <activity>.

My case was one of those three. Starting from the OS docs and assuming "Android 16 broke this" was, I think, the long way around.

Before reading what the OS changed, I check whether my own settings are still at their defaults. That ordering is one I intend to keep for the next big Android change too.

One more note. The SDK 54 notes said Expo planned to flip the default on in SDK 55 or 56. As of November 2026, the SDK 58 reference still says false. That single default is worth rechecking on every upgrade.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦See that Expo (SDK 54 and later) already opts out by default, so back navigation only changes in apps where some setting drifted from that default
✦Compare app.json, the manifest application tag, and the manifest activity tag with one script, and know which apps actually need a device check
✦Split the opt-out between Expo's own setting and a tiny config plugin so it survives every prebuild
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⬡ Dev Tools2026-07-28
Counting what prebuild --clean will erase before you upgrade to Expo SDK 57
A raw diff between two generated ios/ trees showed 649 changed lines; only 3 were real edits. How to count what prebuild --clean erases, and move it into a config plugin.
⬡ Dev Tools2026-10-25
Sound Effects Stop at Play #40 — With expo-audio's createAudioPlayer, remove() Alone Isn't Cleanup
Creating a createAudioPlayer instance per play in expo-audio can leave Android silent after about 40 plays, with didJustFinish never arriving. What remove() and release() each do, three ways to restructure, and how to notice when it happens.
⬡ Dev Tools2026-09-10
I Added a Dim Screen Button, and iPhones Stayed Dark After the App Was Closed
In expo-brightness, setBrightnessAsync applies only to the current activity on Android, but changes the device brightness itself on iOS. Here is why the cleanup burden falls on one platform only, and a hook that restores brightness through AppState.