React Native 0.86: Zero Breaking Changes, Two Releases in a Row

React Native just shipped version 0.86, and it might be the most “boring” release in years — in the best possible way. No sweeping API rewrites, no migration headaches, no “block off two sprints for this” energy. Just a smoother, more polished framework that quietly fixes the things that have been annoying Android developers for a year.

TL;DR: 0.86 fixes Android 15 edge-to-edge bugs that have been silently breaking layouts, adds light/dark mode emulation and a new performance track to DevTools, and — most importantly for planning your roadmap — ships with zero user-facing breaking changes, the second release in a row to pull that off. If you’re on 0.85, this is close to a drop-in upgrade.

Here’s what’s actually new, and why it matters if you’re shipping a React Native app in 2026.

1. Edge-to-Edge Support for Android 15+ Finally Works Properly

Android 15 made edge-to-edge layouts mandatory — whether an app opted in or not. That silently broke a handful of core React Native APIs for apps that weren’t ready for it. 0.86 goes through and fixes the fallout:

• measureInWindow now returns correct coordinates when edge-to-edge is active (previously it could be off by however much space the status/nav bars used to occupy)
• KeyboardAvoidingView correctly calculates available space on Android 15+, so your inputs stop getting covered by the keyboard
• Dimensions window values are now accurate even on older Android versions when edge-to-edge is manually enabled
• StatusBar can update style and visibility while a Modal is open
• The navigation bar now correctly respects enforceNavigationBarContrast from your theme

If your app has been fighting weird layout shifts, mis-measured touch targets, or a keyboard that overlaps your form fields on newer Android devices, this release is probably the fix you’ve been waiting for.

2. React Native DevTools Gets Genuinely Useful Upgrades

DevTools continues to mature into a real debugging tool instead of an afterthought:

• Light/dark mode emulation, powered by Emulation.setEmulatedMedia, lets you test how your app responds to system appearance changes without physically flipping your device's theme
• A new performance trace track for React Native Renderer operations, giving you clearer visibility into what the renderer is actually doing during a slow frame
• The inspector’s reconnect loop now has exponential backoff and better exception handling, so it stops fragmenting heap memory during long debugging sessions — a quiet fix, but a real one if you’ve ever had DevTools itself slow down your machine
• Hermes was bumped to fix missing JavaScript samples in the Performance panel timeline on Apple platforms

Small additions individually, but they close a real gap — testing appearance-based logic and diagnosing render-thread slowdowns used to require awkward workarounds.

3. Smaller Fixes That Add Up

A few quieter but genuinely annoying bugs got squashed:

• Modal's style prop is now forwarded to its inner container View, so you can finally add padding or a background color without breaking transparent or backdropColor
• A flicker bug in Animated — where animated views could briefly snap back to their pre-animation state after a React commit — is fixed via better mounting-layer sync
• PerformanceObserver now defaults durationThreshold to 104ms for event observations, matching the W3C spec, instead of flooding you with every micro-event
• The Cookie header passed via WebSocket's constructor headers option is no longer silently stripped — a real fix for anyone doing cookie-authenticated WebSocket connections
• NetworkingModule now catches OutOfMemoryError instead of crashing your app on very large HTTP responses
• Views with non-invertible transforms (scaleX: 0, scaleY: 0) no longer incorrectly receive touches

4. Zero Breaking Changes — Again

This is the headline that matters most for teams planning their roadmap: 0.86 is the second release in a row (after 0.83) with no user-facing breaking changes. If you’re on 0.85, you should be able to upgrade without touching your app code.

That’s a deliberate strategic shift. React Native has historically had a reputation for upgrades being a mini-project of their own — dependency breakage, native module incompatibilities, layout regressions. The framework’s maintainers now seem to be aiming for a cadence where every other release is guaranteed non-breaking, which changes the calculus for teams that have been hesitant to stay current.

A couple of deprecations to be aware of for future releases, though nothing breaks yet:

• ViewUtil.getUIManagerType is deprecated as part of the ongoing removal of the legacy architecture
• AppRegistry.setComponentProviderInstrumentationHook's second argument is deprecated
• Setting reportErrorsAsExceptions to anything other than false no longer has any effect (previously any falsy value worked)

5. A Bigger Story: React Native Moves to the React Foundation

Beyond the changelog, there’s an organizational shift worth noting: the React Native repo — along with React, Metro, Yoga, and the React Native website — has moved from the facebook GitHub org to a new react org. This reflects React and React Native's transition to the React Foundation, an independent body focused on the long-term stewardship of the ecosystem. GitHub redirects handle all existing links automatically, so there's nothing you need to do — but it's a meaningful signal about where the project is headed institutionally, and worth keeping in mind alongside the "stability first" tone of this release.

Should You Upgrade? A Quick Checklist

If you’re already on 0.85: yes, this is close to a drop-in upgrade. Run through this before you ship it:

• Run npx react-native upgrade or diff against the Upgrade Helper
• Confirm any native/custom modules are compatible (most will be — check recent issues on your most-used packages)
• On Android 15+, explicitly re-test edge-to-edge layouts, keyboard behavior, and any manual Dimensions workarounds you had in place
• Remove any custom edge-to-edge patches you’d previously hacked in — 0.86 likely makes them redundant
• Validate iOS as usual — no regressions expected, but always check

If you’re further behind — especially in the 0.7x range — 0.86 is a good target to work toward, but plan an incremental path (e.g., 0.7x → 0.80 → 0.83 → 0.86) rather than jumping straight there.

To scaffold a new project on the latest version:

bash

npx @react-native-community/cli@latest init MyProject --version latest

Expo users can pull in 0.86 via expo@canary for now, with broader SDK support following shortly after.

The takeaway: React Native 0.86 isn’t flashy, and that’s the point. After years of the framework’s growing pains — new architecture migrations, bridge removal, breaking API changes — this release is a signal that React Native is settling into a more mature, predictable release rhythm. For teams that have been burned by upgrades before, that predictability might be the most exciting feature of all.

Have you upgraded to 0.86 yet? Let me know how the edge-to-edge fixes worked out for your Android layouts in the comments.