Expo and React Native errorExpo: “Native module cannot be null” or “Cannot find native module”

Why Expo Go can’t load it, and the fix

1. 01

   The library has native code that isn’t in Expo Go

   “There is no way to get the native code into the Expo Go app unless it was already included in the bundle that was uploaded to the app stores.” Expo, Development builds FAQ

   Libraries such as react-native-firebase, payment SDKs and some Bluetooth or video packages ship native code. Your JavaScript loads in Expo Go, calls that native code, and finds nothing, so it fails with one of these errors.

2. 02

   Use a development build

   “A development build is essentially your own version of Expo Go where you are free to use any native libraries and change any native configuration.” Expo, Introduction to development builds

   A development build is your app’s own native shell with the dev tools built in. Build it once with EAS or on your own Mac, install it, and keep using npx expo start for JavaScript changes. For EAS, run eas build:configure first if the project has no eas.json, and check the development profile sets developmentClient to true. A first iOS build asks for your Apple account and test devices.

   npx expo install expo-dev-client
   
   # route A: build in the cloud with EAS
   eas build --profile development --platform ios
   
   # route B: build on your Mac instead
   npx expo run:ios
   
   # then, with either build installed
   npx expo start

3. 03

   An Expo package version that doesn’t match your SDK

   “Automatically update any invalid package versions.” Expo, Expo CLI

   Cannot find native module 'ExpoCamera' or a similar Expo name, can also mean its version was installed with npm install instead of npx expo install and doesn’t match your SDK. If a rebuild didn’t help, check and fix all of them at once:

   npx expo install --check
   npx expo install --fix

4. 04

   Already on a development build? Rebuild it

   The installed build only contains the native code it was built with. After adding or upgrading a library with native code, or changing the app config, build again. JavaScript-only changes don’t need a rebuild.

Checked against the vendor’s docs on November 7, 2026: Expo docs: Development builds FAQ (what you can’t do in Expo Go); Expo docs: Introduction to development builds; Expo docs: Expo CLI (install --check and --fix).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

• from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
• from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start

Related: Expo Go project incompatible · Expo “Unable to resolve module” · Expo EAS build failed · React Native text strings must be rendered within <Text>