-
Notifications
You must be signed in to change notification settings - Fork 172
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
Crashing at EXPO SDK 43 #149
Comments
Yes, with the migration from @unimodules now there is a problem.. |
Is there a way of resolve this locally? |
@victorglezcardoso did you find a way to solved it locally as you asked? Tks! |
I face the same issue did any one solve this ? |
cristianFryla No, unfortunately not. I make a walkaround controlling manually in the app the version of the store via a rest request to my server. When I update the app, I change in my server the version of the app and if it is necessary I force the app to update... Cheers. |
Ok, tks, I did the same unfortunaltely!! |
I personally don't use expo, happy to have a pr if someone can |
@rf1804 can you just upgrade the package used on folder related to the package react-native-version-check-expo |
@FatmaMahmoud698 It was already done v3.4.3 was released 12 hours ago https://www.npmjs.com/package/react-native-version-check-expo |
@rf1804 on this path react-native-version-check/packages/react-native-version-check-expo/package.json |
I created a fork, which does not depend on expo-localization. https://www.npmjs.com/package/expo-react-native-version-checker |
Expo has deprecated unimodules and moved to 'expo' package;
https://blog.expo.dev/expo-sdk-43-aa9b3c7d5541
Migrating: https://github.com/expo/fyi/blob/master/expo-modules-migration.md
The text was updated successfully, but these errors were encountered: