-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
[Navigator] renderScene method called for every component in route stack #2536
Comments
@ranyefet - I added This does seem to be a bug, at least with using
Ideally, I believe, we would not re-render the active scene but rather only the upcoming scene. cc @ericvicenti @hedgerwang |
Hi there! This issue is being closed because it has been inactive for a while. But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/navigator-renderscene-method-called-for-every-component-in-route-stack ProductPains helps the community prioritize the most important issues thanks to its voting feature. Also, if this issue is a bug, please consider sending a PR with a fix. We rely on the community to provide |
Hi i am facing this issue for version: React native 0.33.0
I get this output from adb logcat: I/ReactNativeJS( 5126): ***** Renering AppContainer ****** I/ReactNativeJS( 5126): rendering scene: home ..... some more logs Is there a work around for this? |
Hi all,
I'm having a weird bug with Navigator. This is the same issue as #952.
I'm using v0.10.0, basically what happens is that renderScene method is called for every route in the stack.
That causes some weird issues in my app and I think it also affects performance.
I was able to easily reproduce it using
UIExplorer
example.NavigatorExample.js (line 113):
Is it supposed to happen?
Thanks,
Ran.
The text was updated successfully, but these errors were encountered: