[Regression][Navigator] renderScene is called with every route in the routeStack after navigator.push
See original GitHub issue@ericvicenti As per our discussion on irc, I think this is a bug. Not sure though.
Also to reproduce:
Just console.log in renderScene here: https://github.com/facebook/react-native/blob/master/Examples/UIExplorer/Navigator/NavigatorExample.js#L113-L114
[13:50] <Chirag> run the app. goto Navigator and click float in from right. "float in for right" will call render scene with first scene and second scene
Issue Analytics
- State:
- Created 8 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
react navigation, get name of nested route - Stack Overflow
When I try and access from props the current route in my header, like below, the title is undefined , how can I...
Read more >React Native Navigator — Navigating Like A Pro in React Native
is then available in the renderScene method as a property of the route. Let's look at an example: Set up your Navigator like...
Read more >Writing widget tests for navigation events - iiro.dev
Find out how to test push and pop events by using the WidgetTester APIs and mockito. Learn how to tap things. Be bummed...
Read more >Navigator 2.0: Navigation & Routing In Flutter
A page creates a route that gets placed on the route stack. Each page takes a key so that when Navigator uses this...
Read more >Navigate to a new screen and back - Flutter documentation
Terminology: In Flutter, screens and pages are called routes. The remainder of this recipe refers ... Navigate to the second route using Navigator.push()....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m experiencing this problem too. I just pushed the details route after user clicked on an item in the list view and render() gets called multiple times. Performance is really taking a toll.
Hi, I’m running into this issue with v0.21. Is it fixed on a specific version and if so which one would it be?