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.
Related
I am trying to run a react native project on the simulator using expo go. However, I am getting errors.
What I tried:
package.json has the version 34.0.0 for expo.
When running this on the simulator I get the below issue.
I then try to upgrade my expo, but getting an error there too.
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.
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..
Im using Ionic to build an Android app and I'm finding a problem that I cant work around or find an answer to. When I run ionic build android or ionic emulate android I get the following:
Error: Failed do find 'ANDROID_HOME'...
I believe I have added the correct variables to PATH and ANDROID_HOME under System Variables, but please check: http://imgur.com/a/UOdCd
The first image is ANDROID_HOME, the second shows where the sdk is located, the third is the Error itself and the fourth is my path variable.
I run it from Git Bash. Running as an administrator did not make any difference, I also tried reinstalling Android SDK (with Android Studio) in a different folder (was in %HOME%\AppData\Local\Android\ before) without any difference. Also tried to reboot after reinstalling SDK.
I also tried to run the SDK Manager first (C:\Android\sdk\tools\android.bat) and keeping it open while trying to build or emulate, but it still didn't work.
You need to create a new system variable called ANDROID_HOME and as a value put the path to the android SDK installation directory.
For more information, please refer to the installation guide.
I'm trying to run wso2 api manager from the source code. I downloaded carbon4kernel and the product-apim as stated on the site. The code builds successfully and imports into eclipse, but I can't launch the carbon server.
When I execute wso2server.sh I get the following:
Error: Could not find or load main class org.wso2.carbon.launcher.Main
Even if I add the class to the classpath, it finds the Main class, but I get:
SEVERE {org.wso2.carbon.launcher.Main} - org/osgi/framework/launch/FrameworkFactory
This is using the C5 server (although the download seems to suggest carbon4) and apiman 1.9.1.
Its worth noting that the binary distribution works straight out of the box, but uses an older version of carbon (AXIS2-based), but the source code version uses OSGi.
Does anyone have this working, or point me to where its going wrong please?
We don't have any products released on top of C5. So basically at the moment you cannot build API Manager with C5.
About building and running C5, which wso2server.sh did you try to run? I guess you tired with the one at distribution/kernel/carbon-home/bin/wso2server.sh. If that is the case it won't work. What you need to do is, build the project from the root pom.xml and at distribution/kernel/target the built zip file. Unzip it and try the wso2server.sh in the bin directory.
Alternatively, without building from source, you can download and try the C5 kernel binary from https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0