-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
When Farbic is turned on, if the previous page used react native reanimated useAnimatedStyle, it will cause RNSScreen. m's viewDidLayoutSubviews to be called multiple times #6639
Comments
If I use React Native [email protected] Normal in debug mode, but abnormal in release mode |
Same issue here with Expo 52, rn 0.76.1, newest rn-reanimated and rn-screens and react-navigation 7 |
@odogono @javascripter @notjosh Can you take a look at this question? |
@
Try it out [email protected] Whether it can be or not? |
I can still confirm the issue.
The interesting part is if we remove the native header it's not reproducible anymore. Is there any update on this? |
I can confirm this, and also that
In my case, that's causing my
Interestingly, if I tap a button that doesn't have opacity animation, like |
Can confirm this is specifically a Fabric issue. Setting We are seeing bizarre behaviour related to this where we can see the tab bar below pushed stack screens etc, I assume because the screen container can not calculate its height correctly. |
@tjzel How to solve this? |
Description
If I don't use useAnimatedStyle, it's normal. onLayout will only be called once
Steps to reproduce
1.Page A using the AusAnimatedStyle of React Native Reanimated
2.push to page B,this page headerShow is true
3.Page B onLayou Always callback
Snack or a link to a repository
https://github.com/renyufei8023/RNTest
Reanimated version
3.16.1
React Native version
0.74.5
Platforms
iOS
JavaScript runtime
Hermes
Workflow
React Native
Architecture
Fabric (New Architecture)
Build type
Debug app & dev bundle
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: