Menu

What Actually Breaks When You Bump targetSdkVersion to 36 (and How to Fix It)
πŸ“°

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

DEV Community: reactnativeΒ·Pascu EduardΒ·about 9 hours ago
#lSCdykCJ
#devtoreactnative#devto#dev#edge#android
Reading 0:00
15s threshold

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.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.