When trying to build my Expo project, using expo build:ios, I get the following error:
Unsupported SDK version: our app builders don't have support for
33.0.0 version yet. Submitting the app to the Apple App Store may result in an unexpected behaviour Unsupported SDK version
What is causing this error and how can I fix it?
What causes this error?
This error is caused by the fact that as of March 31st 2020 the Expo client no longer supports Expo SDK 33. From the Expo release blog we see the following:
Dropping SDK 33 from the Expo client
We routinely drop SDK versions
that have low usage in order to reduce the number of versions that we
need to support. This release sees the end of life for SDK 33. As
usual, your standalone apps built with SDK 33 will continue to work;
however, SDK 33 projects will no longer work within the latest version
of the Expo client. If you want to re-run expo build, then you’ll need
to upgrade from SDK 33, preferably to SDK 37 so you won’t need to
update again for a while (and also because each Expo version is better
than the last!).
How do I fix this?
To fix this error you need to upgrade the SDK that that your Expo project is using. Ideally you should upgrade to the latest version. In this case Expo SDK 37 as that will give you the longest amount of time until you have to upgrade again.
To upgrade the SDK. Expo has a fantastic resource detailing what you have to do here. Each blog post give steps on how to upgrade.
Here are the basic steps on how to upgrade:
Run expo upgrade in your project directory (requires the latest version of expo-cli, you can update with npm i -g expo-cli).
Make sure to check the changelog for other breaking changes!
Update the Expo app on your phones from the App Store / Google Play. expo-cli will automatically update your apps in simulators if you delete the existing apps, or you can run expo client:install:ios and expo client:install:android.
If you built a standalone app previously, remember that you will need to create a new build in order to update the SDK version. Run expo build:ios and/or expo build:android when you are ready to do a new build for submission to stores.
Make sure you check the changelogs
As you are upgrading from SDK 33 you will need to look at the different changelogs that exist for upgrading from 33 to 34, 34 to 35, 35 to 36, and finally 36 to 37. This is because there could be something that occurred in one of those updates that may break something in your app.
How can I avoid this problem in the future?
Simply, make sure that you keep your apps up-to-date. Upgrading many versions of Expo and/or React-Native can be cumbersome as features are added and removed with each release. The easiest way to stay on top of it is to upgrade frequently, I find that by setting aside a coupe of days a month to check the dependencies etc that I am using are up-to-date means that I do not have to massive upgrades. It also means I am in a better place to know what it going to cause a problem and I have more time to fix it.
tl;dr
Update your Expo SDK version to the latest release.
Incompatible version of SDK..
For me, it worked after updating the Expo app from Google play store..
Related
I have build an app with expo. Let's say version 1.0.10
This app is available on test flight and I can install and check the functionality.
Now, if I find some issue, I use expo publish --release-channel production to fix the same.
Next time when I open my app, I receive the latest updates and issue is fixed.
But the problem is, if I delete the app, and install it again from the test flight, it still has the old version of code i.e. from 1.0.10. To see the latest updates, I have to kill the app and open it again. Is there a way to handle updates correctly? All the new installs should get the latest updates.
I tried multiple updates over version 1.0.10. But the latest updates are not available on new installs. I always have to kill the app and open it again to get the latest, which is not what i want.
Should I include a step to check if updates are available, and if yes, get the latest updates. Build this with version 1.0.11 and try expo publish and see new installs has the latests updates?
i have downloaded a react native project which uses 40.0.0 version of expo go, however my IOS simulator supports the newer version of expo go versions like 41.0.0,42.0.0,43.0.0. how can i deal with this? is it by updating the version of the project ??
that's happening because every few versions that Expo is updated, they deprecate the oldest one.
To fix this is very easy.
1 - Kill the server
2 - run expo upgrade sdk version
3 - run expo start again.
I hope it was helpful. :)
cheers
Exactly. Your problem is that your project expo SDK version is too old (which is not recommended for several reasons, one of which is that you won't be able to upload your project to the stores later).
It is recommended to always have the Expo SDK of your project updated.
I'm getting an odd error now, and this seems to happen no matter what build I deploy. I can switch to a different set of tutorial directories or other folders, run npm start, and on the Expo device on my Android I'll still get this error.
It seems to not matter whether I run Expo SDK 33 or one higher, like 34 or 37. Oddly, I do have a build that sort of works on a different LAN IP. This is odd, because I don't even think I have another build running and this shouldn't pull up, but it does. I'll attach a screen shot here, but I'm really confused as to why this is happening. I can't find any reference (per the screen shot) where the StyleSheet method is missing.
I am running Expo34.0.4 in this build and using the following react-native build reference -
"react-native": "https://github.com/expo/react-native/archive/sdk-40.0.0.tar.gz",
Should I install a specific (different) version of both Expo and React-Native?
This had been working for a while and then suddenly started giving this error.
Thanks!
Do you use the compatible version for your SDK? Use react-native from https://github.com/expo/react-native/archive/sdk-34.0.2.tar.gz for Expo SDK 34.
Each Expo SDK version depends on a React Native version.
I was working on my React Native project with AWS Amplify, everything went well
One day, I tried the AWS Cognito authentification feature I added few weeks ago, and it is not working anymore and I dont understand why. I searched for the error log all over the internet but nothing found.
Please help
When I call the Auth.signIn() method, I get the following error:
Expo managed workflow support for amazon-cognito-identity-js is only available in SDK 39 and higher.
Problem solved, I went through many problem during installations but what made it for me was to install the latest version of expo (expo upgrade) (SDK 39 at least) and update all my package using a npm library:
npm install -g npm-check-updates
ncu
ncu -u
I tried to update my AWSSDK for windows with one released 1 DEC to test a new Lambda with C#.
But I got error message like this.
Product: AWS Tools for Windows -- Error 1722.
There is a problem with this Windows Installer package.
A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor.
Thanks for the report, and we apologize for the inconvenience caused.
As noted by others, for this install we changed how we install the toolkit and for some users this is causing install fails that we have not managed yet to reproduce in-house and are still trying to find root cause for.
Feel free to post your install log here (if you have it), or on the AWS forum thread posted above where we are tracking the problem and gathering data from affected users.
What version(s) of Visual Studio do you have installed, and was this an upgrade install from a previous version?
We released version 1.11.1.4 of the AWS Toolkit for Visual Studio to resolve the installation problems. You can download the latest version from https://aws.amazon.com/visualstudio/