react-navigation / react-navigation/react-navigation
[Android] - Navigation not working properly when new architecture is enabled.
Open
Nobody has claimed this yet.
bug
package:native-stack
package:stack
platform:android
repro provided
- Dominant language
- TypeScript
- Stars
- 24.5k
- Forks
- 5.1k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 18
Description
Current behavior
If we navigate from screen A to B and then go back and navigate to B again it is not working.
If we disable new architecture it is working.
Expected behavior
Should move to next screen on button click.
Reproduction
https://github.com/usmankhan495/TestProject
Platform
- Android
- iOS
- Web
- Windows
- MacOS
Packages
- @react-navigation/bottom-tabs
- @react-navigation/drawer
- @react-navigation/material-bottom-tabs
- @react-navigation/material-top-tabs
- @react-navigation/stack
- @react-navigation/native-stack
Environment
- [] I've removed the packages that I don't use
| package | version |
|---|---|
| @react-navigation/native | 6.0.10 |
| @react-navigation/native-stack | 6.6.1 |
| react-native-safe-area-context | 4.2.4 |
| react-native-screens | 3.13.1 |
| react-native | 0.68.1 |
| node | v17.8.0 |
| yarn | 1.22.18 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked TestProject reproduction and compare navigation behavior with the new architecture enabled and disabled. Check the listed @react-navigation/native-stack, @react-navigation/stack, react-native-screens, and React Native versions. Done means navigating A to B, returning, and navigating to B again moves to the next screen on button click.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100