-
-
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
[Reanimated] Couldn't determine the version of the native part of Reanimated. #4134
Comments
Hey! 👋 It looks like you've omitted a few important sections from the issue template. Please complete React Native version section. |
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? |
expo still do not support V3. |
Expo go do not support new reanimated. Also you might want to be on Expo 48 already. |
@radko93 |
@pouyarezvani Hey did you happen to find a reliable fix for this? I'm using expo SDK 48 and I've tried pretty much everything I can think of with no luck |
Expo continues with it's many problems. I am stuck with this also |
Facing the same issue on my side with Expo 48.0.16 and react-native-reanimated version 2.14.4 |
Same error for me Not an expo project |
Same issue for me,
No expo, IOS platform. |
any solution now? |
I'm having the same problem, using react-native 0.71.8, react-native-reanimated 2.14.4, no expo, IOS platform. It looks like the native component should set "_REANIMATED_VERSION_CPP" when it loads. I can see this in the .mm file in REAInitializer in the npm package, and this is visible in XCode in the Pods project, so it appears to be being built. Somehow it isn't getting copied, or it is failing to initialise. Tracing this through:
Scattering prints through the code in REAModule.mm shows that it is calling installTurboModule() and then stopping (aren't "turbo modules" part of the new framework, while we want to be on the old?)
This version looks like it is half-way between two frameworks. Curious if anyone has got this working recently? |
Facing this w/ "react-native-reanimated": "3.4.2" Migrated from react-natigve-reanimated 2.13.0. We get these errors mostly when we do OTA update. |
still nothing ? |
Hello i currenlty i am using react native version [email protected] and i have the reanimated version 3.5.4 it is working in android simulator but when i am trying to run on my android devices then it's giving this error i had tried many version of reanimated lib but none of them working getting same issues pls someone help me to resolve this issues |
Same issue here with Expo SDK 50.0.2, |
same. |
same issue. "expo": "^50.0.2", |
Yep, upgraded to expo sdk 50 and I'm also seeing this |
I upgraded react-native-reanimated to 3.6.1 which seems to have fixed the issue. |
That's not good on my side though. I upgraded to 3.6.1 and i'm using expo sdk 50 (migrated from sdk 48) but it's still the same |
Everything's working but the warnings are making me crazy. |
I see it with the latest versions |
downgrading expo to "expo": "~49.0.15" fix this issue for me... |
Seeing the same issue. |
Seems like they messed up in the new expo version |
Same, Expo 50 upgrade from 49.... |
facing same issue over Android, no expo |
When using Expo Go, it's important to stick to the recommended version of Reanimated. Expo Go includes a built-in version of Reanimated, so updating the Reanimated version only affects the JS part of Reanimated. Since Expo Go can't be recompiled without calling the |
Description
When Upgrading to version 3 I get the following error.
[Reanimated] Couldn't determine the version of the native part of Reanimated. Did you forget to re-build the app after upgrading react-native-reanimated? If you use Expo Go, you must use the exact version which is bundled into Expo SDK.
I am using Expo Version 37, React Version 18, and reanimated Version "next" and react-native Version 0.70.5
Steps to reproduce
Snack or a link to a repository
https://snack.expo.io/
Reanimated version
3.0.0
React Native version
70
Platforms
iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: