React Native shows Unimplemented component: RNCSafeAreaProvider
Unimplemented component: <RNCSafeAreaProvider>Short answer
The JavaScript side of react-native-safe-area-context is installed but the running app does not have a matching native side. In bare projects run pod install for iOS and rebuild. In Expo, reinstall with npx expo install so the version fits your SDK.
Fix it fast
1Find out which cause you have
Check which library versions are installed and whether you run in Expo Go, a development build or a bare build.
npm ls react-native-safe-area-context react-native-screens2Match what you see, then jump to its fix
What does the error look like?
Unimplemented component: <RNCSafeAreaProvider>
Cause 1 of 2
iOS pods were not installed after adding the library (bare React Native)
1Check
Native libraries need linking on iOS. The React Navigation guide says pod install completes the linking.
ls ios/Pods | grep -i safe2Fix
Install the pods and rebuild the app.
npx pod-install ios
npx react-native run-ios3Verify
Rebuild and open the app; the red screen is gone.
npx react-native run-iosConfirmed by reactnavigation.org
Cause 2 of 2
The version does not match your Expo SDK
1Check
Expo picks versions compatible with your SDK when you use its installer.
npm ls react-native-safe-area-context2Fix
Reinstall with the Expo installer, then restart.
npx expo install react-native-screens react-native-safe-area-context3Verify
Restart Metro with a clear cache; the screen renders.
npx expo start --clearConfirmed by docs.expo.dev
How do I stop it coming back?
- Install navigation dependencies with the Expo installer in Expo projects.
- Run pod install after every native dependency change in bare projects.
- Wrap the app in SafeAreaProvider at the root when not using Expo Router (Expo Router sets it up itself).
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Mobile apps
Android build stops at processDebugManifest in a React Native app
Manifest merger failed
processDebugManifest is the step that merges your AndroidManifest.xml with the manifests of every library.
2 causes, each with a fixMobile apps
Running pod on a React Native project fails with can't find gem cocoapods
can't find gem cocoapods (>= 0.a) with executable pod
The pod command exists, but the Ruby that is running it has no CocoaPods gem.
3 causes, each with a fixMobile apps
React Native Android build cannot find the foojay-resolver-convention plugin
Plugin [id: 'org.gradle.toolchains.foojay-resolver-convention'] was not found in any of the following sources:
The foojay plugin is a settings plugin that Gradle downloads from the Plugin Portal.
3 causes, each with a fixMobile apps
Kotlin and Java compile to different JVM targets in a React Native Android build
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11)
Gradle refuses to build when the Java task and the Kotlin task target different JVM versions.
3 causes, each with a fixMobile apps
Gradle cannot run node in a React Native Android build
Process 'command 'node'' finished with non-zero exit value 1
The React Native Gradle plugin starts node for bundling.
3 causes, each with a fixMobile apps
The Android emulator opens the app but never connects to Metro or Expo
Metro bundler ECONNREFUSED 127.0.0.1:19001
When the emulator cannot reach Metro, first prove each side on its own: adb sees the emulator, and Metro listens on its port.
4 causes, each with a fix