-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Replace does not work with Tabs scene #2404
Comments
I am facing the same issue where a reset throws an error saying that no route was defined and a replace doesn't actually replace the current scene. |
Having same issue. |
+1 |
facing same issue |
causes the following error:
Here my env
|
@dittmarconsulting downgrade RNRF to .27 |
Please try to reproduce it with Example project and latest version 4.0.0-beta.40. Feel free to open if the issue still exists |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Tell us which versions you are using:
Expected behaviour
I want to have the scene replaced (or reset - although reset doesn't work either) when I navigate to specific scenes.
Actual behaviour
The history stack is still available so users can swipe back on IOS and android users can use the hardware back button. I don't want to remove the back ability across the entire app, I just want to reset/replace the stack.
Steps to reproduce
I have tried the following implementations with no luck from the Landing scene (check below for code):
Actions.replace('SceneTabs')
Actions. SceneTabs({type:'replace'})
Actions. SceneTabs({type:Actions})
Actions. SceneTabs({type:ActionConst.REPLACE})
All of the above methods do not work. I tried them with reset as well and it doesn't work. In v3 I was able to do
Actions.SceneTabs({type:'reset'})
without issue.The below method does work for REPLACE only - still won't work with RESET.
UPDATE:
After looking deeper into closed PR's, it appears this fix #2344 was closed.
I don't fully understand all the implications of this PR but it might be worth taking another look at because I've seen numerous closed issues about replace/reset due to inactivity - I hope the issues didn't go inactive because people chose another router
The text was updated successfully, but these errors were encountered: