Skip to content
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] pop animations hang and lag slowly in 0.14.2 #4132

Closed
jforaker opened this issue Nov 14, 2015 · 16 comments
Closed

[Navigator] pop animations hang and lag slowly in 0.14.2 #4132

jforaker opened this issue Nov 14, 2015 · 16 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@jforaker
Copy link

https://www.dropbox.com/s/6ze2xllvmzrrk79/2015_11_15_16_45_56.mp4?dl=0

Ever since upgrade to 0.14.2, Navigator pop() animations hang and look laggy overall. As you can see in the video the view being popped "hangs" for noticeably too long, then abruptly disappears. This is not ideal and seems like a regression in terms of performance, and or is a definite bug.

Yes it is Genymotion, yes dev mode is false, tested on brand new Nexus 5x - same thing. It was flawless before in 0.13.x
(Disregard the animation lag in the view pushes, I'll chalk that up to the emulator performance. Just pay attention to the back arrow clicks and the 'X' button clicks)

First view being pushed is:

sceneConfig: Navigator.SceneConfigs.FloatFromBottom

Second one is:

Navigator.SceneConfigs.FloatFromRight

screen-recording-2015-11-15-16-59-33-qk4rbd8yrs

@praisegeek
Copy link

It seems to affect Scene Configs with longer transitions.
You can use Navigator.SceneConfigs.FadeAndroid for now until a fix has been made.

@brentvatne
Copy link
Collaborator

cc @mkonicek this is an example of where offloading animations is good ;)

@brentvatne brentvatne changed the title Android Navigator pop animations hang and lag slowly in 0.14.2 [Navigator] pop animations hang and lag slowly in 0.14.2 Nov 15, 2015
@brentvatne
Copy link
Collaborator

Not seeing any changes to Navigator.js that landed in 0.14 that would have impacted this. Are you sure that this was the only change that you made? Are you not maybe running some code in response to navigator focus events?

@jforaker
Copy link
Author

Can you elaborate on what you mean by "navigator focus events"?

@brentvatne
Copy link
Collaborator

@jforaker
Copy link
Author

Definitely not, never used that before. As far as I understand, I am just doing simple pushes and pops, and passing in sceneConfig to mix it up the animations for the user.

@satya164
Copy link
Contributor

Is this fixed in master? Cause this is there in 0.15.0-rc

The relevant issue - #3669

@brentvatne
Copy link
Collaborator

Thanks for additional context @satya164! Are you guys only experiencing this on Android?

@satya164
Copy link
Contributor

@brentvatne I've not tested on iOS yet.

@brentvatne
Copy link
Collaborator

@mkonicek - are you seeing this at all internally? not sure who should be assigned

@jforaker
Copy link
Author

Same, not tested on iOS for me.

Here is a higher res/better video showing the problem: https://www.dropbox.com/s/6ze2xllvmzrrk79/2015_11_15_16_45_56.mp4?dl=0

Also note the crazy angled animation on the last view that occurs with:

sceneConfig: Navigator.SceneConfigs.VerticalUpSwipeJump

@ramilushev
Copy link

+1 I can confirm this is happening on Android. Just simple push and pop, nothing else. Could this be a problem with animating the opacity?

@kmagiera
Copy link
Contributor

kmagiera commented Dec 2, 2015

This issue should be fixed in 0.16 as of #3954. @jforaker, would you be able to verify that on your app and close this issue? Thanks!

@jforaker
Copy link
Author

jforaker commented Dec 3, 2015

Installing react-native@latest (which was 0.16.0-rc) did not work at all for me, see #4488 (comment).

When using 0.16.0-rc:
TypeError: expected dynamic type 'double', but had type 'boolean' (constructing arguments for RCTNetworking.sendRequest at argument index 5)

0.15.0 is the most recent version that I can actually get to run successfully without red screen errors on start. Therefore I cannot say if this issue is fixed or not.

Is there a way to install this specific "version" that I am unaware of? Installing a library at a certain pull request is not the most straightforward thing to do...

@satya164 - have you got it to work? Or have you seen the transition animations be fixed in your app?

@satya164
Copy link
Contributor

satya164 commented Dec 4, 2015

@jforaker I cannot upgrade to RN to 0.16.0-rc due to babel issues #4327

But if I cherry-pick b12117a, then the issue goes away.

@satya164
Copy link
Contributor

satya164 commented Dec 5, 2015

Closing this since this has been fixed with b12117a

@satya164 satya164 closed this as completed Dec 5, 2015
@facebook facebook locked as resolved and limited conversation to collaborators Jul 20, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

7 participants