Crashing at EXPO SDK 43
See original GitHub issueExpo has deprecated unimodules and moved to ‘expo’ package; https://blog.expo.dev/expo-sdk-43-aa9b3c7d5541
unable to resolve
> 1 | import { NativeModulesProxy } from '@unimodules/core';
Migrating: https://github.com/expo/fyi/blob/master/expo-modules-migration.md
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Expo Go and other Expo SDK app crashes on first load ...
When you are installing the normal Expo Go app from the Google Store (or other app using Expo SDK) on a Samsung Android...
Read more >Troubleshooting build errors and crashes - Expo Documentation
This particular error means that the app is importing ./src/Routes and it is not found. The cause could be that the filename case...
Read more >Expo EAS build android apk crash on physical device
npm install react-native-safe-area-context then run expo doctor --fix-dependencies to make it compatible with your sdk version. or directly run ...
Read more >Expo built app crash on Testflight | Apple Developer Forums
I had the same problem since the last expo update. The problem is due to 2 modules which are react-native-picker-select and react-native-shadow- ...
Read more >Expo App on IOS crashes when using Auth Session for Spotify ...
I've had some issues with expo auth session. I've also had some super random app crashes lately - an input that without a...
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 FreeTop 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
Top GitHub Comments
Yes, with the migration from @unimodules now there is a problem… Should be changed to
import { NativeModulesProxy } from 'expo-modules-core'
Is there a way of resolve this locally?