react-native-reanimated: TypeError: ReanimatedModule.installTurboModule is not a function
Description
Following error is beeing thrown when try to use createAnimatedComponent method
Error: Requiring module “node_modules\react-native-reanimated\src\createAnimatedComponent.tsx”, which threw an exception: TypeError: ReanimatedModule.installTurboModule is not a function
except adding plugins: [‘react-native-reanimated/plugin’] is there anything I have to do regarding to the package configuration?
Expected behavior
Actual behavior & steps to reproduce
Snack or minimal code example
import Animated from ‘react-native-reanimated’
Animated.createAnimatedComponent(HStack)
It applies to other methods as well. For example
useSharedValue(0)
throws the same exception.
Package versions
±- @babel/core@7.17.8 ±- @react-navigation/drawer@6.4.1 ±- @react-navigation/native@6.0.10 ±- @types/react@17.0.43 ±- @types/react-native@0.64.24 ±- @types/shortid@0.0.29 ±- expo@44.0.6 ±- expo-linking@3.0.0 ±- expo-status-bar@1.2.0 ±- moti@0.17.1 ±- native-base@3.3.10 ±- prettier@2.6.1 ±- react@17.0.1 ±- react-dom@17.0.1 ±- react-native@0.64.3 ±- react-native-checkbox-reanimated@0.1.1 ±- react-native-gesture-handler@2.3.2 ±- react-native-reanimated@2.5.0 ±- react-native-safe-area-context@4.2.4 ±- react-native-screens@3.13.1 ±- react-native-svg@12.3.0 ±- react-native-web@0.17.1 ±- shortid@2.2.16 ±- styled-components@5.3.5 ±- styled-system@5.1.5 `-- typescript@4.3.5
name | version |
---|---|
react-native | 0.64.3 |
react-native-reanimated | 2.5.0 |
NodeJS | 14.16.1 |
expo | 44.0.6 |
Affected platforms
- Android
- iOS
- Web
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 17
- Comments: 25 (2 by maintainers)
I am also getting on version 2.8.0
I am also getting this lately while running jest tests.
“react-native-reanimated”: “^2.3.2”, “jest”: “^26.6.3”,
Same issue with
Same issue with 2.8.0
I have the same issue and nothing helps
It might help someone: we updated expo to 45 but jest-expo was still in 44. Updating to 45 fixed this issue for us.
Same same