-
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
Tabbar Navigation always goes back to the last screen #2026
Comments
It seem ReactNavigation behaviour, but maybe I didn't understand issue. I want to repeat, screenshots only are not helpful for me, I need runnable project also. |
Possible it's a ReactNavigation behavior but I didn't have this issue when I using React Navigation. |
It is about 'backBehavior' for TabNavigator. It is set to 'none' by RNRF: |
I would suggest using initialRoute I believe that is more of the expected behavior |
- Enhancement: support inheritance of scene props (useful for `headerMode` attribute for different RN StackNavigator animation) - Fix: attempt to fix react-navigation pushes instead of jumping when user taps the same tab (#2024) - Enhancement: use navBarButtonColor or tintColor or headerTintColor for image button tintcolor (#2028) - Fix: use backBehavior='initialRoute' by default (#2026) - Enhancement: allow right/leftTitle, right/leftButtonImage to be static functions within scene component - Enhancement: allow wrapping all screens and navbar buttons with `wrapBy` parameter for `Router`. It could be `observer` from MobX, or `connect` from Redux or any other function. - Fix: eslint formatting, fix CircleCI build
I've removed 'none' as back behaviour but don't see any changes. Maybe you could check ReactNavigation itself for desired behaviour. |
I'm version 8 beta
I have a tabbar
Tab 1
Tab 2
If I'm on the teams view and move onto the photos view and then click on the tab 1 I'm taken to the teams view the last view I was on, but I should be taken to the home view which is the first view for tab 1.
The text was updated successfully, but these errors were encountered: