Incompatible with Expo 38
See original GitHub issueBug
The current Expo version (38) only supports react-native-reanimated 1.9. It looks this package is using useValue which was introduced in reanimated 1.10.
I’m not sure if there are other methods that this package depends that makes it incompatible with Expo 38.
Environment info
Library | Version |
---|---|
@gorhom/bottom-sheet | 1.1.1 |
react-native | 0.62 (Expo 38) |
react-native-reanimated | ~1.9 |
react-native-gesture-handler | ~1.6.0 |
Steps To Reproduce
Render the component and get the following error:
(0, _reactNativeReanimated.useValue) is not a function. (In '(0, _reactNativeReanimated.useValue)(0)', '(0, _reactNativeReanimated.useValue)' is undefined)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Incompatible react native SDK with expo SDK
When I run react native project using expo I got this error "This project uses SDK 38.0.0 but this version of Expo Go...
Read more >I cant upgrade my expo sdk to 39 and above stuck on ...
i have tried expo update, expo update 42.0.0 yet when i run my build it says upgrade to sdk 39 or above SDK...
Read more >Setting / upgrading Expo SDK
If you absolutely need to use a Bare workflow for an unsupported Expo module, my advice to everyone (both developers and Draftbit users)...
Read more >expo-updates
For bare workflow projects, if the expo package is installed, it must be version 37.0.2 or later. Finally, this module is not compatible...
Read more >Expo SDK 38 is now available
Check out the React Native changelog for more details. Flipper is currently unsupported in the Managed workflow. If you want to use Flipper,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I currently use it with reanimated 2 and it is working totally fine, maybe try installing reanimated yourself again using expo/npm/yarn
Was this fixed in 2.0.2?