-
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
Reset stack on enter Scene? #2104
Comments
One way to do it on a route is to just put |
@alexwasner Tried that. Didn't work. |
Looks like |
@luco Have you tried |
@aksonov Still not working. Tried both |
@luco In my case Actions.reset("homeMain") is working. Try that. |
@luco Could you reproduce it with latest Example? I used Actions.tabbar({type:'replace'}) with 4.0.0-beta.14 and tabbar replaces launch screen normally. |
@aksonov It gives me this error: My structure is like this:
|
Remove type='reset' from scenes. Use it as parameter. Again, please reproduce it with current Example project. |
@aksonov is this incorrect Actions.reset("homeMain") ? I am able to reset the back stack using it. |
@rajsuvariya When I try this method, it only allows me to pick scenes outside my root. |
@aksonov Ok, you want to reproduce with example project, but this doesnt solve my problem. I want to understand what im doing wrong. |
@aksonov Figured it out. It was the way my Scenes where nested. Had to do this way:
Last question: |
Try type='replace' |
I'm getting a warning of maximum call stack when I perform a Do you have idea why? |
Nervemind. Typo. |
@luco Given your routing structure:
How did you reset the stack when navigating from
|
Actions.usersList({ type:'replace' }) |
thanks @aksonov sir, your solution worked for me. |
Tks @rajsuvariya works for me ! |
Is it possible to reset the stack when entering on a scene?
I mean, I want to push from a scene to tabbar, but when reach the tabbar, reset the stack.
Is that possible?
I already tried
Actions.homeMain({type: ActionConst.RESET})
Didn't work.
The text was updated successfully, but these errors were encountered: