Question 1

How do I fix "Unable to resolve module" in React Native or Expo?

Accepted Answer

This error comes from Metro, the React Native bundler, and means it could not find a file or package that your code imports. Work through it in order. First, check the package is actually installed: run npx expo install with the package name in an Expo project, or npm install in a bare project. Second, check the import path and the exact filename casing. macOS is case-insensitive, so ./Button and ./button both work locally, but EAS Build and most CI machines run Linux, which is case-sensitive, so the build fails there. Third, clear the Metro cache with npx expo start --clear, because Metro can keep a stale module map after you move or rename files. If the module is a path alias like @/components, confirm the alias is configured in tsconfig.json or babel.config.js and that Metro picks it up. Paste the full error into this tool and it will point to the most likely cause for your setup.

Question 2

Why does my app crash in Expo Go with "native module not found"?

Accepted Answer

Expo Go is a prebuilt app that only contains the native modules included in the Expo SDK. When you install a library that ships its own native iOS or Android code and it is not part of the SDK, Expo Go has no way to load it, so you see errors like TurboModuleRegistry.getEnforcing could not be found, requireNativeComponent was not found in the UIManager, or Cannot find native module. Reinstalling the package will not help. The fix is to switch to a development build, which is your own version of Expo Go compiled with every native library your project uses. Install expo-dev-client, then build locally with npx expo run:ios or npx expo run:android, or in the cloud with eas build using a development profile. After that, any time you add or upgrade a native library, rebuild the development build, because a JavaScript reload does not pick up new native code.

Question 3

How do I fix "VirtualizedLists should never be nested inside plain ScrollViews"?

Accepted Answer

React Native shows this warning when a FlatList or SectionList is placed inside a ScrollView that scrolls in the same direction. The outer ScrollView renders the whole list at once, which defeats the virtualization that keeps long lists fast, so you get slow scrolling, high memory use and broken onEndReached behaviour. The proper fix is to remove the wrapping ScrollView and let the list own the scrolling. Move any content that sat above or below the list into the FlatList ListHeaderComponent and ListFooterComponent props. If the screen has several groups of items, use a single SectionList instead of several FlatLists. Silencing the warning with LogBox.ignoreLogs hides the message but leaves the performance problem in place, so treat that only as a temporary measure. This tool can rewrite your screen code into the recommended structure when you paste it with the error.

Question 4

How do I fix "Text strings must be rendered within a <Text> component"?

Accepted Answer

In React Native every piece of text has to live inside a Text component, unlike the web where text can sit directly inside a div. This error means something produced a raw string or number outside a Text element. Common causes are a stray space or character between JSX tags, a variable that holds text rendered directly inside a View, and conditional rendering with the && operator when the left side is a number. For example, if count is 0, the expression count && a component renders the number 0 itself, which crashes on native. Fix it by making the condition a real boolean, such as count > 0 && the component, or by using a ternary that returns null. Also check for text written next to an icon or inside a Pressable without its own Text wrapper. Paste the error with the component code and this tool will highlight the exact line to change.

Question 5

How do I fix an EAS Build or CocoaPods failure?

Accepted Answer

When an EAS Build fails, the last lines of the log usually just say the build phase failed. The useful information is earlier. Open the failed build on expo.dev, expand the phase that failed, such as Install pods or Run gradlew, and scroll up to the first real error message. On iOS, CocoaPods failures often come from mismatched native library versions or an outdated pod spec repo. In a bare project run pod install with the repo-update flag inside the ios folder, and in a project that uses Continuous Native Generation regenerate the native folders with npx expo prebuild --clean instead of hand-editing them. On Android, Gradle failures are frequently caused by incompatible library versions or the wrong Java version, since current React Native versions expect JDK 17. Running npx expo-doctor and npx expo install --fix before building catches many of these version mismatches early.

Question 6

Is it safe to paste my error logs into this tool?

Accepted Answer

Before anything is sent, the page scans your error log and code for things that look like credentials, such as API keys, access tokens, JWTs, private keys, Bearer headers, passwords in configuration lines and passwords inside connection strings, and replaces them with a REDACTED placeholder. The server runs the same check again. This catches the common formats, but it cannot recognise every possible secret, so you should still remove anything sensitive before pasting, especially custom tokens or customer data. The tool only needs the error message, the stack trace and the code around the failing line to diagnose the problem. A short summary of each request is logged to help us improve the tool, and logged error text is trimmed. No account or signup is needed to use the error fixer.

Error	Usual Fix
Unable to resolve module	Install the package, fix the path or filename casing, clear the Metro cache
TurboModuleRegistry.getEnforcing(...) could not be found	Use a development build instead of Expo Go, then rebuild
VirtualizedLists should never be nested	Move content into ListHeaderComponent / ListFooterComponent
Text strings must be rendered within a <Text>	Wrap the text, or make && conditions real booleans
Invalid hook call	Call hooks only in components; check for duplicate React with npm ls react
Each child in a list should have a unique "key"	Pass a stable keyExtractor or key, not the index
Unable to load script	Start Metro; on Android USB run adb reverse tcp:8081 tcp:8081
pod install failed / Gradle build failed	Align versions with npx expo install --fix, read the first error in the build log

Error	Usual Fix
Unable to resolve module	Install the package, fix the path or filename casing, clear the Metro cache
TurboModuleRegistry.getEnforcing(...) could not be found	Use a development build instead of Expo Go, then rebuild
VirtualizedLists should never be nested	Move content into ListHeaderComponent / ListFooterComponent
Text strings must be rendered within a <Text>	Wrap the text, or make && conditions real booleans
Invalid hook call	Call hooks only in components; check for duplicate React with npm ls react
Each child in a list should have a unique "key"	Pass a stable keyExtractor or key, not the index
Unable to load script	Start Metro; on Android USB run adb reverse tcp:8081 tcp:8081
pod install failed / Gradle build failed	Align versions with npx expo install --fix, read the first error in the build log

Free React Native & Expo Error Fixer

How to Debug a React Native Error

Common React Native & Expo Errors

Expo Go vs Development Builds

Frequently Asked Questions

How to Debug a React Native Error

Common React Native & Expo Errors

Expo Go vs Development Builds

Frequently Asked Questions