Google Play raises its target API level requirement every year, and 2026's is a big one. Since August 31, 2026, new apps and app updates must target Android 16 (API level 36). If your React Native or Expo app targets anything lower, Play Console will reject your next update.
Targeting API 36 isn't just a version bump. Android 16 changes how apps are laid out, how they behave on large screens and how the back gesture works. Here's what changes and how to migrate. (If you own the app rather than build it, our plain-English guide for business owners explains the rule and what the fix involves.)
The rules
| App type | Requirement |
|---|---|
| New apps and updates (phones, tablets) | Target API 36 or higher |
| Wear OS and Android Automotive OS | Target API 35 or higher |
| Existing apps that don't update | Target API 35+ to stay visible to new users on newer Android versions |
Some developers were granted extensions to November 1, 2026, which have now passed. If you can't publish an update today because of target API level, this migration is now urgent.
Step 1: Get onto a current toolchain
Expo apps: Expo SDK 54 and later (React Native 0.81+) target API 36 by default. Upgrading the SDK is the cleanest path, ideally to the current SDK:
npx expo install expo@latest --fix
npx expo-doctor@latest
If you need to pin the values explicitly, use expo-build-properties:
{
"expo": {
"plugins": [
[
"expo-build-properties",
{
"android": {
"compileSdkVersion": 36,
"targetSdkVersion": 36
}
}
]
]
}
}
Bare React Native apps: React Native 0.81 is the first version that targets Android 16 by default. On an older version, upgrade React Native rather than only changing targetSdkVersion in Gradle, since older versions weren't tested against Android 16's behavior changes.
Google Play checks the target SDK in the merged manifest inside your app bundle, so verify the final AAB rather than just your config.
Step 2: Fix edge-to-edge layouts
This is the change most likely to make your app look broken. Apps targeting API 36 can't opt out of edge-to-edge, so the window extends behind the status bar and navigation bar. Expo has made edge-to-edge the default and SDK 54 uses React Native's built-in support.
What to check:
- Headers and bottom content under system bars. Use
react-native-safe-area-contextinsets rather than hard-coded padding. React Native's built-inSafeAreaViewis deprecated as of 0.81. - Status bar colors. Setting a status bar background color no longer applies. Draw your own background behind the inset area if you need one.
- Keyboard handling. Forms with
KeyboardAvoidingVieworadjustResizethat worked before can leave inputs hidden under the keyboard. Test every form, and considerreact-native-keyboard-controllerfor consistent behavior. - Bottom sheets, tab bars and floating buttons. Make sure they clear the gesture navigation bar.
Expo Router's Stack and native tabs handle insets for you, which is a good reason to rely on them instead of custom headers.
Step 3: Test on tablets and foldables
For apps targeting API 36, Android ignores orientation locks, resizability limits and aspect-ratio restrictions on large screens (smallest width of 600dp or more). Games are excluded. If your app was portrait-only, it will now rotate and resize on tablets, foldables and desktop windows.
Test on a tablet emulator and a foldable emulator, rotating and resizing. Use useWindowDimensions instead of reading screen size once at startup, and let lists and grids reflow.
Step 4: Check back-button behavior
Android 16 continues the move to predictive back, where the system shows a preview of where the back gesture will go. For apps targeting API 36 on Android 16 devices, the predictive back animations are on by default and the old onBackPressed callback is no longer called.
In React Native, test anything that overrides back: BackHandler listeners that close modals, "are you sure you want to leave?" prompts on forms, and custom back behavior inside nested navigators. If something stops working, update React Native and your navigation libraries first. As a temporary measure you can opt out with android:enableOnBackInvokedCallback="false" in the manifest while you fix it.
Step 5: Native libraries and 16 KB pages
Google Play also requires apps targeting Android 15 and later to support 16 KB memory page sizes. React Native 0.77 and later, and current Expo SDKs, build compatible binaries. The risk is older third-party libraries that ship prebuilt native .so files. Play Console flags non-compliant bundles, and Android Studio's APK Analyzer shows which library is the problem.
This is also a good moment to remove native dependencies you no longer use. Each one is something that can break on the next Android release.
A migration checklist
- Upgrade Expo or React Native to a version that targets API 36.
- Update native libraries, especially navigation, keyboard, camera, maps and payments.
- Rebuild and confirm
targetSdkVersion 36in the merged manifest. - Walk every screen on an Android 16 device or emulator for edge-to-edge issues.
- Test every form with the keyboard open.
- Rotate and resize on tablet and foldable emulators.
- Test back gestures and
BackHandlerlogic. - Check Play Console's pre-launch report before rolling out, then use a staged rollout.
This happens every year
API 37 will follow on the same yearly cycle, and iOS has its own deadline: the iOS 27 UIScene requirement. Teams that upgrade in small steps through the year spend a day or two on each deadline. Teams that wait spend weeks. If you're planning the budget, our app maintenance cost guide breaks it down.