Yesterday, i’ve tried to run my react-native project with a simulator on iOS (OS - macOS). However, randomly i’ve got an error on Expo XDE Desktop that the experience couldn’t be loaded because it uses an supported Expo SDk version (15.0.0).
upon searching online, i found that deleting Expo app from the simulator (i’m running Ipad Air 2) helps - I did that and then ran npm run ios --simulator="ipad air 2" again, but the issue persists.
i’ve updated react-native and expo-sdk to their latest versions. the issue is still there.
on desktop, when running my IOS app on the tunnel, it works fine until I scan the QR code with tablet for testing - it throws the same error as above. i deleted the expo app from the actual tablet as well - no success.
what’s happening here? why did it stop working all of a sudden? i’ve been looking for solutions for the past 3h, but no cigar. any help is much appreciated. thanks.
We periodically remove support for old versions of the Expo SDK from the Expo app so that the app doesn’t get too too big. With the latest release, we just removed support for SDK 15.
If you built a standalone app that uses SDK 15, it will still work, but it will be hard to make changes to it since you won’t be able to use the Expo app.
This is in general a good practice and will get you bug fixes and performance improvements usually that are nice to have. And will make it easier to upgrade – and use new stuff and generally keep up with the current state of the ecosystem – if you do this periodically.
Hope that makes sense and is helpful.
Again, if you published a standalone app, it will continue to work as is, but you should upgrade to a newer SDK to continue development.
Hello! thanks for the answer. However, after updating Expo, I ran into dependency hell situation as my app refuses to work when trying various versions of react-native and other libs.
The error of an outdated SDK is no longer there, but there’s a new one - TypeError: undefined is not an object (evaluating '_expo.Components.KeepAwake')
how do I solve this error? is this because of an unsupported react or react-native version?