-
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
Issue popping down to root StackNavigator #1987
Comments
Could you fork and modify Example to show what exactly do you want to achieve? If so, probably I have to add |
thanks! please check out: Only changes are in Example/components/TabView.js To replicate, At tab2_2, there doesn't seem to be any way to pop back to the Launch screen. |
Please check latest master |
@aksonov thanks for so quickly pushing a fix! could you deploy it to npm so I can test it with the complex Scene hierarchy I have in my app right now? |
It should be deployed already
… 10 июля 2017 г., в 18:49, Alexander Chia ***@***.***> написал(а):
@aksonov thanks for so quickly pushing a fix!
could you deploy it to npm so I can test it with the complex Scene hierarchy I have in my app right now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
works great in beta7. amazing work! |
Version
Tell us which versions you are using:
In a project that is set up like this:
<Scene key='root'> <Scene key='login'> <Scene key='main' tabs> <Scene key='tab1'> <Scene key='settings1'> <Scene key='settings2'> </Scene> <Scene key='tab2'> ...
Assume that right now we are on tab1, and that stacknavigator has ['settings1', 'settings2'] where settings2 is at the top.
From the Settings2 scene, it seems to be extremely difficult, if not possible to pop down to the scene 'login'.
Actions.login() does not work (an undefined error pops up)
The hack
Actions.reset('login') doesn't even work, and
we only get options available in the current stackNavigator.
(Error: there is no route defined for key 'login', Must be one of 'tab1', 'settings1', 'settings2')
Furthermore, the Actions.popTo() function from v3 seems to have been removed.
The example in v4 still has code that uses this inexistent function.
--
I think this issue is stemming from
when a project is set up as StackNavigator 1 > TabNavigator > StackNavigator 2,
scenes in Stacknavigator 2 are unable to pop us back down to StackNavigator 1.
Right now without a popTo function, there seems to be no way to do so in the current framework.
The text was updated successfully, but these errors were encountered: