react-native-reanimated icon indicating copy to clipboard operation
react-native-reanimated copied to clipboard

[Reanimated] Couldn't determine the version of the native part of Reanimated.

Open pouyarezvani opened this issue 1 year ago • 28 comments

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 avatar Mar 01 '23 10:03 pouyarezvani

Hey! 👋

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

Please complete React Native version section.

github-actions[bot] avatar Mar 01 '23 10:03 github-actions[bot]

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?

github-actions[bot] avatar Mar 01 '23 10:03 github-actions[bot]

expo still do not support V3.

arasrezaei avatar Mar 01 '23 10:03 arasrezaei

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

radko93 avatar Mar 01 '23 14:03 radko93

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

pouyarezvani avatar Mar 01 '23 19:03 pouyarezvani

@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

brandon2580 avatar Mar 23 '23 00:03 brandon2580

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

AnatuGreen avatar Apr 18 '23 10:04 AnatuGreen

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

FCartier avatar May 08 '23 07:05 FCartier

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

Not an expo project

camchis avatar Jul 19 '23 10:07 camchis

Same issue for me,

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

No expo, IOS platform.

powerpivar avatar Jul 19 '23 12:07 powerpivar

any solution now?

fukemy avatar Jul 27 '23 08:07 fukemy

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?

iainb123 avatar Aug 04 '23 08:08 iainb123

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.

prayaslashkari avatar Aug 24 '23 13:08 prayaslashkari

still nothing ?

awesomedan93 avatar Nov 01 '23 10:11 awesomedan93

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…

Aakash359 avatar Dec 13 '23 17:12 Aakash359

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",

teddybee avatar Jan 18 '24 22:01 teddybee

same.

bobOnGitHub avatar Jan 19 '24 06:01 bobOnGitHub

same issue.

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

kiyohken2000 avatar Jan 19 '24 16:01 kiyohken2000

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

demfabris avatar Jan 19 '24 21:01 demfabris

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

ewein avatar Jan 19 '24 21:01 ewein

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 avatar Jan 19 '24 23:01 Shazam72

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

Shazam72 avatar Jan 19 '24 23:01 Shazam72

I see it with the latest versions

ikaasraa avatar Jan 21 '24 14:01 ikaasraa

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

ananduremanan avatar Jan 22 '24 10:01 ananduremanan

Seeing the same issue.

phillippschmedt avatar Jan 22 '24 20:01 phillippschmedt

Seems like they messed up in the new expo version

ananduremanan avatar Jan 23 '24 12:01 ananduremanan

Same, Expo 50 upgrade from 49....

AlexNodex avatar Jan 24 '24 13:01 AlexNodex

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

ambikaKum avatar Mar 01 '24 11:03 ambikaKum