No view found for id ... for fragment ScreenStackFragment...

[Medkhat]

Current behavior

Hi there! I have a problem with @react-navigation/native-stack. After several screen jumps the application crashes.

Note: all configuration is correct (MainActivity.java, pods, etc.)

Example here

Screen.Recording.2023-11-26.at.04.38.33.mov

Expected behavior

I want a help with this

Reproduction

I attached video example. Code is common

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• @react-navigation/native-stack
• react-native-tab-view

Environment

• [✅] I've removed the packages that I don't use

package	version
@react-navigation/native	6.1.9
@react-navigation/bottom-tabs	6.5.11
@react-navigation/native-stack	6.9.17
react-native-safe-area-context	4.7.4
react-native-screens	3.27.0
react-native-gesture-handler	2.14.0
react-native-reanimated	3.5.4
react-native	0.72.7
node	20.9.0
npm or yarn	yarn@1.22.19

[github-actions]

Hey @Medkhat! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

• Expo Snack
• TypeScript Playground
• GitHub repo under your username

A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

[yangm97]

I think I have this issue.

Are you using freezeOnBlur on your BottomTabs?

[Medkhat]

@yangm97 Hi! I'm using the standard features which in the docs

[steveacalabro-indevets]

+1

[pc9]

@Medkhat Try setting detachInactiveScreens={false} https://reactnavigation.org/docs/bottom-tab-navigator/#detachinactivescreens. Worked for me.

[danidaryaweesh]

I'm also experiencing this issue on RN 0.73.1 and latest React-navigation version. I tried the react-native paper integration solution and it works with no issues. Have anyone found any solution for this?

[danidaryaweesh]

Worked for me by disabling Fabric (new architecture) for now.

[gdaghero]

same

[github-actions]

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.

[vnijat]

@Medkhat Try setting detachInactiveScreens={false} https://reactnavigation.org/docs/bottom-tab-navigator/#detachinactivescreens. Worked for me.

Thank you @Medkhat, this worked for me too RN 0.73.5

[github-actions]

Hey! This issue is closed and isn't watched by the core team. You are welcome to discuss the issue with others in this thread, but if you think this issue is still valid and needs to be tracked, please open a new issue with a repro.

[wallycarvalho]

@Medkhat Try setting detachInactiveScreens={false} https://reactnavigation.org/docs/bottom-tab-navigator/#detachinactivescreens. Worked for me.

Thank you @Medkhat, this worked for me too RN 0.73.5

It appears this solution worked for me as well. I have a similar scenario where I have a stack navigator running inside a drawer with Fabric enabled. Switching the flag in the drawer navigator options has prevented the error from surfacing.

[foyarash]

I am encountering the same issue

Expo 51
RN 0.74.1
RNS 3.31.1
react-navigation/native-stack 6.9.26
react-navigation/native 6.1.17
react-navigation/bottom-tabs 6.5.20

[tonypangs]

i am experiencing this too
"react": "18.2.0",
"react-native": "^0.72.7",
"@react-navigation/bottom-tabs": "^6.5.11",
"@react-navigation/native": "^6.1.9",
"@react-navigation/native-stack": "^6.9.17",
"@react-navigation/stack": "^6.3.20",