react-native-reanimated: app crashes if debugging mode is enabled

Fixed in release https://www.npmjs.com/package/react-native-reanimated/v/2.4.0

It looks like this was only fixed on iOS, any word on a fix for Android?

I was on react-native-reanimated version 2.3.1 and after upgrading it to 2.4.1, it worked. Thank you @valery-lavrik

This is not related just to reanimated and the debugger support is not a thing reanimated can “fix”, since it’s because of react native architecture (or better, turbo modules). While it’s annoying that the app just crashes when you enable remote debugging, it doesn’t seem that reanimated can do anything more than adding a huge warning box to the installation instructions.

• Like the box there says, you can use Flipper to debug your app.
• Some tips on how to debug were also mentioned in RN’s Turbo Modules topic. You can try using Safari to debug iOS app.
• There are also special Hermes debugging instructions.
• With expo it’s more complicated as you can find in their documentation. You can follow the feature request and try this workaround in the meanwhile.
• You can join the discussion at react native’s proposal repo and propose a solution. Or just subscribe.

I can confirm this doesn’t work on android, I am also getting the error “Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.” Using latest version 2.5.0

By any chance, did you find a solution @anutting?

It was fixed for me after being updated to react-native-reanimated 2.4.0

Thanks @valery-lavrik For me, it just worked by updating to react-native-reanimated 2.4.1

npm i react-native-reanimated@next

@jakub-gonet Thank you for your response and suggestion.

I m not sure if it is appropriate to ask here. Can you please have a look at this Stack Overflow question regarding Flipper, if you have time?