Open andreialecu opened 1 year ago
Hey! 👋
The issue doesn't seem to contain a minimal reproduction.
Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?
I know how to fix it, the PR will be available soon 👍
Our QA team also observed such freeze issues during navigation in release android app
Great! Is it fixed @piaskowyk? I am experiencing the same issue with react-native 0.67.5 and react-native-reanimated 3.3.0.
If I upgrade to react-native-reanimate 3.4.2 or above, I am getting a type error, so as of now, I have to stick to 3.3.0...
Description
Been experimenting with Shared Element Transitions and have been getting this crash.
I think a variant of this also happens on Android, but it only occurs when going from Screen A to B to C, then back to B, then A. There's a freeze of the entire screen and it cannot be interacted with any more. If I hit the physical back button this is logged:
Steps to reproduce
I can reproduce this with React Navigation when using a custom
headerBackground
for a bunch of screens. It occurs when navigating from screen A > B then back to A. Note that this was just an experiment to see if I could transition the header.Snack or a link to a repository
n/a
Reanimated version
3.4.2
React Native version
0.71.6
Platforms
iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes