React Navigation throws 'you have nested a NavigationContainer inside another'
Error: Looks like you have nested a 'NavigationContainer' inside another.Short answer
React Navigation allows one NavigationContainer for the whole app. The error means a second container renders somewhere inside the first one's tree. Find it and delete it, because nested navigators go inside screens and need no container. Only if you truly want a separate tree, wrap that container in NavigationIndependentTree.
Fix it fast
1Find out which cause you have
List every file that renders a NavigationContainer. The app should have exactly one, in the root component. Any other hit is a suspect.
grep -rn "NavigationContainer" --include=*.tsx --include=*.jsx --include=*.js --include=*.ts app src components screens 2>/dev/null2Match what you see, then jump to its fix
- 1
More than one file in the grep output renders <NavigationContainer>, and the error appears as soon as that screen mounts.A screen or child component wraps its own NavigationContainerFix - 2
The nested container is deliberate, for example a self-contained flow with its own history, and the error text itself suggests NavigationIndependentTree.You want a second, fully separate navigation treeFix
- 1
What does the error look like?
Error: Looks like you have nested a 'NavigationContainer' inside another.If this was intentional, wrap the container in 'NavigationIndependentTree' explicitly.
Cause 1 of 2
A screen or child component wraps its own NavigationContainer
1Check
Open each extra hit. A common source is a screen file copied from a tutorial or an example that carried its own App wrapper, so the screen renders a container while already inside the root one.
// Root: this is the only place a container belongs
<NavigationContainer>
<RootStack />
</NavigationContainer>2Fix
Delete the extra container and return the navigator directly. A navigator rendered inside a screen of another navigator is how nesting works, and it needs no container of its own.
// before: inside HomeTabs.tsx
// return (<NavigationContainer><Tab.Navigator>...</Tab.Navigator></NavigationContainer>);
// after
export function HomeTabs() {
return (
<Tab.Navigator>
<Tab.Screen name="Feed" component={FeedScreen} />
</Tab.Navigator>
);
}
// and the stack registers it as a screen
<Stack.Screen name="Home" component={HomeTabs} options={{ headerShown: false }} />3Verify
Reload the app. The red screen is gone.
npx expo start --clearConfirmed by reactnavigation.org
Cause 2 of 2
You want a second, fully separate navigation tree
1Check
Decide whether that flow really needs to be disconnected from the parent. The docs say an independent tree cannot navigate to or from the rest of the app, so an ordinary nested navigator is usually what you want.
grep -rn "NavigationIndependentTree" src app2Fix
Wrap only that inner container in NavigationIndependentTree, imported from @react-navigation/native.
import { NavigationContainer, NavigationIndependentTree } from '@react-navigation/native';
export function EmbeddedFlow() {
return (
<NavigationIndependentTree>
<NavigationContainer>
<FlowStack />
</NavigationContainer>
</NavigationIndependentTree>
);
}3Verify
The error no longer appears. Remember that navigate() calls inside the flow cannot reach screens outside it.
npx expo start --clearConfirmed by reactnavigation.org
How do I stop it coming back?
- Keep the single NavigationContainer in the root component and nowhere else.
- Build each part of the app as a navigator or a screen, never as a small app with its own wrapper.
- Search for NavigationContainer when you paste a screen or example from another project.
- Use NavigationIndependentTree only for flows that must be cut off from the main navigation.
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
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix