Skip to content
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

Closed
pouyarezvani opened this issue Mar 1, 2023 · 29 comments
Labels
Missing info The user didn't precise the problem enough Missing repro This issue need minimum repro scenario Needs review Issue is ready to be reviewed by a maintainer Platform: iOS This issue is specific to iOS

Comments

@pouyarezvani
Copy link

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.

image

I am using Expo Version 37, React Version 18, and reanimated Version "next" and react-native Version 0.70.5

Steps to reproduce

  1. upgrade to reanimated version 'next/3' and
  2. Run expo GO
  3. and get that error

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

@pouyarezvani pouyarezvani added the Needs review Issue is ready to be reviewed by a maintainer label Mar 1, 2023
@github-actions github-actions bot added Platform: iOS This issue is specific to iOS Missing info The user didn't precise the problem enough Missing repro This issue need minimum repro scenario labels Mar 1, 2023
@github-actions
Copy link

github-actions bot commented Mar 1, 2023

Hey! 👋

It looks like you've omitted a few important sections from the issue template.

Please complete React Native version section.

@github-actions
Copy link

github-actions bot commented Mar 1, 2023

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?

@arasrezaei
Copy link

expo still do not support V3.

@radko93
Copy link
Contributor

radko93 commented Mar 1, 2023

Expo go do not support new reanimated. Also you might want to be on Expo 48 already.

@pouyarezvani
Copy link
Author

@radko93
Do you know how soon we can start using v3?
Thanks

@brandon2580
Copy link

@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

@AnatuGreen
Copy link

Expo continues with it's many problems. I am stuck with this also

@FCartier
Copy link

FCartier commented May 8, 2023

Facing the same issue on my side with Expo 48.0.16 and react-native-reanimated version 2.14.4

@camchis
Copy link

camchis commented Jul 19, 2023

Same error for me
"react-native": "^0.70.7"
"react-native-reanimated": "2.14.4"

Not an expo project

@powerpivar
Copy link

Same issue for me,

"react": "18.2.0"
"react-native": "0.72.3"
"react-native-reanimated": "2.14.4"

No expo, IOS platform.

@fukemy
Copy link

fukemy commented Jul 27, 2023

any solution now?

@iainb123
Copy link

iainb123 commented Aug 4, 2023

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:

  • npm packages can include a ".podspec" file. I can see one of these in the react-native-reanimated folder. This is scanned by "pod install" and results in the creation of a "pod".
  • React Native creates an XCode project for all of the pods. Building this compiles the native components.
  • The main XCode project seemingly doesn't link directly to the pods, but does so through custom build steps specified in "Build Phases".

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?)

  • _REANIMATED_VERSION_CPP is set in REAInitializer.mm in REAJSIExecutorRuntimeInstaller().
  • This is only called in UIResponder+Reanimated.mm in jsExecutorFactoryForBridge()
  • jsExecutorFactoryForBridge() is mentioned on https://reactnative.dev/docs/0.68/new-architecture-app-intro, suggesting this is for the new architecture, not the old.
  • there's a comment in REAModule.mm's installTurboModule "TODO: Move initialization from UIResponder+Reanimated to here", but this doesn't appear to be completed until version 3.

This version looks like it is half-way between two frameworks. Curious if anyone has got this working recently?

@prayaslashkari
Copy link

Facing this w/

"react-native-reanimated": "3.4.2"
"react-native": "0.70.10"

Migrated from react-natigve-reanimated 2.13.0. We get these errors mostly when we do OTA update.

@awesomedan93
Copy link

still nothing ?

@Aakash359
Copy link

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
Uploading 7ddcf101-2471-4672-9ef4-d316d472ca56.JPG…

@teddybee
Copy link

Same issue here with Expo SDK 50.0.2,
npx expo install --fix is not fixing this warning.
"expo": "^50.0.2",
"react-native": "0.73.2",
"react-native-reanimated": "~3.6.0",
"@react-navigation/drawer": "^6.6.6",

@bobOnGitHub
Copy link

same.

@kiyohken2000
Copy link

kiyohken2000 commented Jan 19, 2024

same issue.

"expo": "^50.0.2",
"react-native-reanimated": "~3.6.0",

@demfabris
Copy link

Yep, upgraded to expo sdk 50 and I'm also seeing this

@ewein
Copy link

ewein commented Jan 19, 2024

I upgraded react-native-reanimated to 3.6.1 which seems to have fixed the issue.

@Shazam72
Copy link

Shazam72 commented Jan 19, 2024

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

@Shazam72
Copy link

Shazam72 commented Jan 19, 2024

Everything's working but the warnings are making me crazy.
Gotta build it with the warnings, the client want his app tomorrow

@ikaasraa
Copy link

I see it with the latest versions

@ananduremanan
Copy link

downgrading expo to "expo": "~49.0.15" fix this issue for me...

@phillippschmedt
Copy link

Seeing the same issue.

@ananduremanan
Copy link

Seems like they messed up in the new expo version

@AlexNodex
Copy link

Same, Expo 50 upgrade from 49....

@ambikaKum
Copy link

facing same issue over Android, no expo
"react-native-reanimated": "3.6.1",
"react-native": "^0.73.1",

@piaskowyk
Copy link
Member

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 prebuild command, there's a possibility of a mismatch between the JS part and the native part of Reanimated, which could lead to crashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Missing info The user didn't precise the problem enough Missing repro This issue need minimum repro scenario Needs review Issue is ready to be reviewed by a maintainer Platform: iOS This issue is specific to iOS
Projects
None yet
Development

No branches or pull requests