goBack() goes to 1st screen on windows! after updating from RN 0.64 to 0.74
Current behavior
I have navigation between native-stack and bottom-tabs. when I goBack() from native-stack it goes to the firest screen!
Expected behavior
It is working fine in both ios and android and also on react-native 0.64. Recently, I am working on updating to 0.74.
Reproduction
Not aviable
Platform
- [ ] Android
- [ ] iOS
- [ ] Web
- [X] Windows
- [ ] MacOS
Packages
- [X] @react-navigation/bottom-tabs
- [ ] @react-navigation/drawer
- [ ] @react-navigation/material-top-tabs
- [ ] @react-navigation/stack
- [X] @react-navigation/native-stack
- [ ] react-native-tab-view
Environment
- [x] I've removed the packages that I don't use
| package | version |
|---|---|
| @react-navigation/native | ^6.1.17 |
| @react-navigation/bottom-tabs | ^6.5.20 |
| @react-navigation/drawer | ^6.6.15 |
| @react-navigation/material-top-tabs | ^6.6.13 |
| @react-navigation/stack | ^6.3.29 |
| @react-navigation/native-stack | ^6.9.26 |
| react-native-safe-area-context | ^4.10.5 |
| react-native-screens | ^3.32.0 |
| react-native-gesture-handler | ^2.17.1 |
| react-native-reanimated | ^3.12.1 |
| react-native-tab-view | ^3.5.2 |
| react-native-pager-view | ^6.3.3 |
| react-native | 0.74.2 |
| expo | - |
| node | v18.18.0 |
| npm or yarn | yarn-3.6.4 |
Hey @asaadbaw! 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.
Couldn't find version numbers for the following packages in the issue:
-
@react-navigation/drawer -
@react-navigation/material-top-tabs -
react-native-tab-view
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.
updated
Hey! Thanks for opening the issue. Seems that this issue is related to react-native-screens library which is a dependency of React Navigation. Can you also post your issue in this repo so that it's notified to the maintainers of that library? This will help us fix the issue faster since it's upto the maintainers of that library to investigate it.
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.