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.
Related
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.
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..
I have to eject from expo in my react native project, but I still want to maintain some functionalities provided by their libraries, like notifications. Is it possible?
Thanks in advance!
Starting with SDK33 Expo was changed to install its own modules separately as required. If you have installed and used the notification module using expo install, you can use it normally even with an eject.
Check whether a module is available on MainApplication.java for Android or info.list for ios.
I am trying to upgrade my Ionic environment to the latest version.
I have an existing app I built on Ionic 2.0.0-beta.32. I want to upgrade it to the latest version 2.0.1 (or the final release).
My questions are :
1) How can I upgrade my environment ?
2) Is there any changes I have to do in my code ? (if yes please can you tell me exactly how to proceed it... ?)
answering question 1:
try these in the root of your project
sudo npm install -g ionic
ionic lib update
question number 2 is hard to answer. generally you should be good. You should try running your code and do some regression testing and then ask specific questions if you face any problems.
Ionic provides upgrade instructions in their changelog. Usually it is enough to upgrade your package version, but sometimes when there are breaking changes that you need to manually address they will be listed on that page.
I built an app in Monaca, and have successfully deployed and published it on google play and the App Store. I know I have to sign it with visual studio to publish it in the windows store, but can manually install it using powershell for development purposes. However, even though it works on android and ios, it crashes immediately after launching in Windows 10. I read over the documentation, and my question is: Is it even compatible? Everything in the documentation is either outdated or stictly for windows 8.
Yes they are compatible. I finally installed and ran it successfully.