React Navigation: the action NAVIGATE was not handled by any navigator
The action 'NAVIGATE' with payload {"name":"Details","params":{}} was not handled by any navigator.Short answer
React Navigation looked for a screen with the name you passed and found none in the current navigator or its parents. Check that the name matches a registered screen exactly, use the screen and params form for screens inside a nested navigator, and do not navigate to screens that a login condition has not rendered yet.
Fix it fast
1Find out which cause you have
Read the payload in the message. The name value is what navigate received; compare it with the screen names you registered.
grep -rn "navigation.navigate\|<Stack.Screen\|name=" src app 2>/dev/null2Match what you see, then jump to its fix
- 1
The payload name is a typo, a different case, or something that is not a screen name at all, such as a URL or an idThe route name does not match a registered screenFix - 2
The name is correct, but the screen is inside another navigator, such as a tab or a drawerThe target screen lives in a nested navigatorFix - 3
It happens right after sign-in or sign-outThe screen is rendered only under a conditionFix
- 1
What does the error look like?
The action 'NAVIGATE' with payload {"name":"Details","params":{}} was not handled by any navigator.The action 'NAVIGATE' was not handled by any navigator
Cause 1 of 3
The route name does not match a registered screen
1Check
React Navigation says the name must match a screen name exactly. List the registered names and compare with the payload.
grep -rn "Stack.Screen\|Tab.Screen\|Drawer.Screen" src app 2>/dev/null2Fix
Pass the exact registered name as the first argument and put values you want to send in the params object, not in the name.
// registered as <Stack.Screen name="Details" ... />
navigation.navigate('Details', { url: serverUrl });3Verify
Tap the button again; the screen opens and no development error shows.
npx react-native start --reset-cacheConfirmed by reactnavigation.org
Cause 2 of 3
The target screen lives in a nested navigator
1Check
Actions bubble up to parent navigators, but a screen in a child navigator that has not rendered is not found. The nesting guide passes the target through the screen key.
grep -rn "createBottomTabNavigator\|createNativeStackNavigator\|createDrawerNavigator" src app 2>/dev/null2Fix
Navigate to the parent screen and name the nested screen in the second argument, adding params next to it.
navigation.navigate('More', {
screen: 'Messages',
params: { id: 7 },
});3Verify
The nested screen opens with its params.
# open the screen in the app; the red error is goneConfirmed by reactnavigation.org
Cause 3 of 3
The screen is rendered only under a condition
1Check
Screens that appear only when a condition is true (a logged-in user, for example) are not registered while it is false. The troubleshooting page warns about navigating manually after the condition changes.
grep -rn "isSignedIn\|user ?\|token ?" src app 2>/dev/null2Fix
Do not call navigate for the screen that the condition itself reveals. Switch the condition, and React Navigation shows the right screen on its own.
{isSignedIn ? (
<Stack.Screen name="Home" component={HomeScreen} />
) : (
<Stack.Screen name="SignIn" component={SignInScreen} />
)}3Verify
After signing in, the app shows Home with no navigate call and no error.
# sign in and watch the screen changeConfirmed by reactnavigation.org
How do I stop it coming back?
- Keep route names in one constants file and import them in both the navigator and the navigate calls.
- Type your param list so a wrong name fails at compile time.
- Send data in params, never as the route name.
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