Maaz Zindani

Loading the index…

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

React Navigation: the action NAVIGATE was not handled by any navigator

ErrorThe 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.

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

Fix it fast

  1. 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/null
  2. 2Match what you see, then jump to its fix

    1. 1The 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. 2The 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. 3It happens right after sign-in or sign-outThe screen is rendered only under a conditionFix

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/null

2Fix

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-cache

Confirmed by reactnavigation.org

Did this fix it?

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/null

2Fix

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 gone

Confirmed by reactnavigation.org

Did this fix it?

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/null

2Fix

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 change

Confirmed by reactnavigation.org

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

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