Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

React Navigation crashes: requireNativeComponent RNSScreenStackHeaderConfig was not found

ErrorrequireNativeComponent: "RNSScreenStackHeaderConfig" was not found in the UIManager

Short answer

The native part of react-native-screens is missing from the app you are running. Either the package is not installed, or it was added after the last native build so the running binary does not contain it. Install it the right way for Expo or bare React Native, run pod install on iOS, and rebuild the app.

  • Applies to React Navigation 7, react-native-screens 4, React Native 0.8x, Expo SDK 54
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check that react-native-screens is a dependency and see which version is installed.

    npm ls react-native-screens
  2. 2Match what you see, then jump to its fix

    1. 1npm ls prints (empty) or the package is missing from package.jsonreact-native-screens is not installedFix
    2. 2The package is in package.json, but the red screen stays after a Metro reloadThe native app was not rebuilt or pods are not installedFix

What does the error look like?

  • requireNativeComponent: "RNSScreenStackHeaderConfig" was not found in the UIManager
  • requireNativeComponent: "RNSScreen" was not found in the UIManager
  • ViewManager returned null for either RNSScreen or RCTRNSScreen

Cause 1 of 2

react-native-screens is not installed

1Check

React Navigation lists react-native-screens and react-native-safe-area-context as required install steps. Look in package.json.

grep -n "react-native-screens\|react-native-safe-area-context" package.json

2Fix

In an Expo project install with npx expo install so the version fits your SDK. In a bare project use npm install.

# Expo
npx expo install react-native-screens react-native-safe-area-context

# bare React Native
npm install react-native-screens react-native-safe-area-context

3Verify

npm ls shows one version of each package.

npm ls react-native-screens react-native-safe-area-context

Confirmed by reactnavigation.org

Did this fix it?

Cause 2 of 2

The native app was not rebuilt or pods are not installed

1Check

React Navigation says missing native views mean the package is missing or the app was not rebuilt. A JavaScript reload does not add native code to an installed app.

ls ios/Pods 2>/dev/null | head -n 3

2Fix

On macOS run pod install in ios/, then clear the Metro cache and rebuild the app. In Expo, rebuild the native app after installing native packages too.

cd ios && pod install && cd ..
npx react-native start --reset-cache
npx react-native run-android   # or run-ios

3Verify

The app opens on the first screen of your stack without the red error.

npx react-native run-android

Confirmed by reactnavigation.org

Did this fix it?

How do I stop it coming back?

  • After adding any package that has native code, rebuild the app instead of only reloading JavaScript.
  • Install with npx expo install in Expo so library versions match the SDK.
  • Run pod install after dependency changes on iOS.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.