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
Tabs do not navigate correctly! #1257
Comments
Does this still occur when you clear the focus on the input before navigating? |
@matthamil It does always happen when the focus isn't cleared yet, but it also happens on random other occasions. |
Does this still occur if you disable the animation that happens when you navigate between tab screens? The animation could be locking the JS thread while you attempt to navigate to other screens, which causes the delay. Add |
@matthamil That does not fix it. Still the late trigger of the action. |
CC: @satya164 |
This btw only appears to happen on Android, IOS seems smooth. |
Can you use master branch instead? |
@satya164 I changed it in my package.json file reinstalled but it still doesn't work. It does however hides my tabbar for some reason, anyway to get it back while staying on master? I adapted the code for the icons in the tabbar to tabBarIcon and adapted header: {style:{}} to headerStyle, so that shouldn't be it I think. "react-navigation": "^1.0.0-beta.9" |
hi |
@MatthieuPeyrot Looks like the same problem, did your tabbar also dissapear with the latest update? |
@bramvbilsen it didn't dissapear , but when i desable the swipe , it's not doing the swipe loop. but i need the swipe. |
Any update on this? |
Any new ? |
@MatthieuPeyrot I haven't found a solution so far... |
i run into the same issue a few days ago. I think i maybe fixed it by flattening my nav structure. @bramvbilsen have you tried placing HomeTabs and OtherScreensStack... into your root navigator? This works for me:
|
Had this problem but now it is not reproducing. Not sure if I'm doing things in a bit kinky way. My stack
I added react https://github.com/satya164/react-navigation-addons and enhanced tabnavigator. Now I get focus/blur states on tabs via listeners. On each tab I have
Bad and dirty? Probably. Worked for me for now :) |
Pinging OP @bramvbilsen since this issue is quite old and related to an old version of the lib. If no answer I'll close in 7 days. It may have been fixed via |
Hi there @bramvbilsen , In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it. If you are still having the issue (especially if it's a bug report) please open a new issue that uses the new Issue Template to provide some more details to help us solve it. |
First of all, I'm sorry if the title is unclear. I had no idea how to call it...
But here is the problem: My tabnavigator gets confused(?) and starts going back to other tabs automatically for some reason. I'll try to explain it more, but first...
The layout of my router looks a bit like this:
`
First I noticed that my tabnavigator was slow in updating titles but that wasn't a huge issue for me. But now, the randomly jumping back to previous tabs is something that simply can't happen. Here is a gif that shows the problem:
Like you can see, the titles don't update instantly as expected and in the end the title shows "Find users" while the page showing is actually the "Home" page.
I figures some code would be useful so here it is:
The stack with the tabnavigator in:
`
export const HomeStack = StackNavigator(
}`
The actual tabnavigator:
`export const HomeTabs = TabNavigator(
);`
I'm sorry, it's really a hard thing to explain. But hopefully it's clear.
Anyone with some help?
Update
I think the reason because of this unwanted behavior is because the page changes instantly when I press the tab, but the navigate action only gets fired +- 10 seconds later. Navigating to other pages out of the tabnavigator result in instant navigate actions on my devices.
react-navigation@1.0.0-beta.8
react-native-cli: 2.0.1
react-native: 0.42.0
The text was updated successfully, but these errors were encountered: