Open nandorojo 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?
Like I said, this is a prod memory issue (I think) so it can't be repro'd in an Expo snack.
Hey @nandorojo, thanks for submitting this issue.
Aside from the root cause of this problem, I believe that ReanimatedReentrancyCheck
should be present only in debug build. The contents of the struct are wrapped inside #ifndef NDEBUG
. If you're getting this stack trace in the release mode, I'm afraid we don't set NDEBUG
properly.
Hey @tomekzaw, thanks for the update. Appreciate the quick fix, hope it addresses the issue.
This issue is still happening for us by the way:
Using Expo SDK 50 and Reanimated 3.8.1
:
Same issue here
Any update? Same issue for us, happens to users in production only, Expo SDK 50 and Reanimated 3.6.2, not device or OS version specific.
Description
I have gotten the following error on Sentry a few times since shipping Reanimated 3.3 to production:
The stack trace on Sentry shows that it has to do with Reanimated:
Let me know if you need more info.
Steps to reproduce
I'm currently not able to reproduce this since it happens very rarely and in production.
Snack or a link to a repository
https://github.com/software-mansion/react-native-reanimated/issues/4901
Reanimated version
3.3.0
React Native version
0.72.3
Platforms
iOS
JavaScript runtime
Hermes
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes