DEV Community

Pascu Eduard
Pascu Eduard

Posted on

What Actually Breaks When You Bump targetSdkVersion to 36 (and How to Fix It)

#reactnative

Google Play requires target API 36 from November 1, 2026 (extension available in Play Console). If you've been putting off the upgrade, here's what's actually going to break — and it's not the version bump.

The version bump is the easy part

Changing targetSdkVersion to 36 in your build.gradle or app.json takes 30 seconds. What happens next is the real work.

The edge-to-edge trap

API 36 removes the edge-to-edge opt-out. On Android 15 (API 35), you could add this to your theme to keep the old behavior:

<item name="android:windowOptOutEdgeToEdgeEnforcement">true</item>
Enter fullscreen mode Exit fullscreen mode

On API 36, this no longer works. Your app content will draw behind the status bar and gesture area unless you handle insets on every screen.

If you use Theme.AppCompat.Light.DarkActionBar and rely on the default Action Bar, your content will start appearing behind the action bar. If you have bottom navigation, it'll be hidden behind the gesture pill.

The fix (the part nobody prices correctly)

For React Native / Expo:

  • Use react-native-safe-area-context for proper edge-to-edge layout
  • React Native 0.81+ has edgeToEdgeEnabled Gradle property
  • Check every screen for status bar / navigation bar overlap

For native Android:

  • Call WindowCompat.enableEdgeToEdge(window) after super.onCreate()
  • Use WindowInsetsCompat to add padding where content overlaps system bars
  • android:fitsSystemWindows="true" on root layouts is a quick fix

What else changes

  • Predictive back is enforced — test your back button handling
  • StatusBar backgroundColor and translucent props stop working (use react-native-edge-to-edge instead)
  • Modal statusBarTranslucent and navigationBarTranslucent are always true
  • App orientation/size restrictions ignored on large screens
  • adjustPan keyboard behavior is broken in edge-to-edge mode

My 12-step checklist

  1. Bump targetSdkVersion to 36
  2. Build and note every visual regression
  3. Fix edge-to-edge insets on every screen (the big one)
  4. Test on Android 15+ physical devices
  5. Check status bar, navigation bar, gesture area
  6. Test keyboard behavior
  7. Verify predictive back works
  8. Check landscape/large screen behavior
  9. Test modal and bottom sheet rendering
  10. Verify no content draws under cutouts
  11. Run full test suite
  12. Build release AAB and verify on device

I also have a diagnosis script and verification script — if you're stuck, I put together a rescue kit: Expo API-36 Android Release Rescue Kit

Good luck before Nov 1 — it sneaks up fast.

Disclosure: This post references my own product.

Top comments (0)