React-native-navigation: Navigation push event is triggered multiple times

Created on 29 Apr 2017 · 5Comments · Source: wix/react-native-navigation

Hi, I'm currently building a four-tab app. Every time, when I switch my app root from singleScreenApp to tabBasedApp, the pre-rendering time is too long which may take me around 2s. During this two-seconds, if I press any button within these four tabs more than once, the onPress event will be triggered multiple times after 2s.

For example, if I press a button to push a new screen multiple times within 2s, says 5 times, then the same new screen will be pushed five times after around 2s.

I found that if I press any button after componentDidMount() callbacks were triggered in all tabs, there are no issues at all. I guess this might be related to the processing of pre-rendering all tabs. In the case of building a complex app, rendering all tabs' component right after launching an app will take a long time, during these few seconds, all button press event will be queued and waited until all tabs are rendered. However, this behaviour is wrong, what is correct is that when each tab is rendered, the buttons inside that tab should be able to press instead of waiting and triggering multiple times.

🏚 stale

Source

gameboyVito

👍4 👀1 😕1

All 5 comments

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest version and report back. Thank you for your contributions.