Mateusz Łopaciński

Let me know if it helps. You can reopen the issue if you still encounter the problem after the upgrade.

So you tried to use reanimated `3.9.0` with RN `0.74.7`, right? Have you reinstalled `node_modules`? You can clean up the project with the `git clean -Xdf` command called from the...

@devendra-dangi Please read the error message again. It already provides a solution: > [Reanimated] Unsupported React Native version. Please use 78 or newer.

@devendra-dangi You must be using reanimated `3.19`. I've just checked sources of the released `3.18.0` version and it has min supported version set to `0.75`: ```rb minimalReactNativeVersion = 75 if...

`3.18.0` should be compatible, so downgrade from `3.19.1` to `3.18.0` or upgrade React Native to `0.78`.

@Neon-jeff It is not possible that you are getting this missing `react-native-worklets` on Reanimated v3. Can you please validate your dependencies and check which version of `reanimated` is really installed?...

Thanks @joacub for reporting the issue. I was able to reproduce it on the Old Architecture (the New Architecture works fine) but this definitely should also work on the Old...

@genesiscz > is there currently a way to get the correct stack trace for the Warnings about the .value being pulled from the JS thread? Unfortunately, there's currently no way...

Simplified reproduction example: Tested on RN 0.78 / Reanimated 3.17.1 | No scrolling | `scrollTo` | maunal scrolling | |-|-|-| | | | | Code snippet ```tsx import { StyleSheet,...

Hey @mozzius! Thanks for reporting the issue. I was able to track down the culprit - in short, we are disabling the exiting animation in CPP just before the component...