-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When navigating to a stack, route state of this stack is undefined #11985
Comments
I have the same issue on react native 0.72.2 and similar navigation packages version. |
@matpoz why did you close it? you found another solution? |
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. |
@AptypTheKing "The route prop passed to components often contained a state property which held state of the child navigator. While it wasn't meant to be public and we recommended against using it in the docs, we've seen a lot of people use this property. Although this is not exactly the same case (I don't intend to use the route prop at all), this shows that this probably doesn't work by design. I haven't found a solution. |
Current behavior
Expected behavior
The nested stack is rendered and so is a screen within the stack.
The state property containing the name and index of the currently rendered route should already be accessible.
Reproduction
https://snack.expo.dev/WDITwptdY68Ahe_pf0wwW
Platform
Packages
Environment
The text was updated successfully, but these errors were encountered: