I need to modify some of the code for the React-Native project that was made a long time ago.
Its Expo Sdk version is 33, and it needs to be updated to the latest version to run the app on Expo Go.
However, updating expo version will inevitably modify many codes. So I hope to use the version as it is without updating it.
Is there any other way to run the app without updating Expo?
Thank you.
Related
Whats the issue?
I get a version mismatch on react native (android).
React Native version mismatch. JavaScript version: 0.59.9 - Native version: 0.63.4
The build works as described in this issue when running through Android Studio. The build however works fine when running: react-native run-android.
Please let me know what else I can try, or what might cause the issue.
React Native version: 0.63.4
Expected Results
The app running as expected
What have I tried to resolve the issue
Clearing caches
Forcing versions through build.gradle
(React Native version mismatch)
Going back in history through git
Reinstalling / trying other emulator versions
Remove node_modules and reinstall
Tried react-native-clean-project
(https://github.com/pmadruga/react-native-clean-project)
Uninstalling
the app from the emulator manually
Was building with SDK Tools 29, also tried with 30 (was working with 29 before)
Tried different versions of Android Studio (4.1, 4.0, 4.1.1. (current))
Tried downgrading to RN 0.62.2
Tried downgrading to RN 0.63.3
Console Error
My "nuclear" option that usually works is to just delete the entire repo from my local machine and then pull it back down from the cloud and start completely fresh.
Definitely not ideal, but sometimes literally nothing else works. I'm not even sure what causes this error as it just appears out of the blue and usually I haven't upgraded react-native for months or even years before it decides to show up.
Are you using a library (3rd party) that is using a react-native version different than your project's react native version?
in my case i was using react-native-v8 in my project and upon upgrading my rn project's version i got this error, so i matched the versions in the correct way.
here is the link for more info, i guess these problems have a similar source.
React Native version mismatch
In the notice of the update of android studio, in red letters as above
Plugin incompatible with the new build found: Firebase Services
I get a warning as above,
I don't understand the meaning.
Does this mean that Firebase related packages will not work after updating android studio?
Should I not update android studio?
However,I think that there seems to be no option to never update android studio
I'm currently building an app using Flutter and Firebase,
but depending on the project, the version of the Firebase related package
may be different, what should I do?
There is no error with my android studio. i am using on Ubuntu.
Late but answering for future help.
Android studio have plugin market place (you can find it at File->setting->plugin). Whenever android studio plans to release an update, it gives beta release first. Meanwhile, most of the plugins, update their plugin accordingly.
In your case, you are facing a warning because Firebase Services plugin had not ready the update for the time being, but in some cases, the plugins release their updates which will be available after you update the android studio. So it is safe to update to the latest android studio.
If you still facing plugin incompatibility warning, disable the plugin until the update will live. It happens only if you are using the low rated plugin. Sometimes, incompatibility warning also appears if your android cache become mess for the system. So cleaning the cache from C:\Users\username\AppData will resolve the issue. Or you can also choose to remove the old android studio files while updating the android studio. But there might be cases that your system do not remove files completely, so remove them manually.
since I installed the lasted update of android studio I have been receiving a lot of errors while trying to run and building the project. I wonder if there is a solution to restore android studio to the older version
You could uninstall android studio and download its older version from here. But the better treatment is to keep the latest version and solve errors.
I have recently upgraded Cordoova to version 6 with android platforms 5.1.0 and ios 4.0.1 in one of the projects.
After also upgrading all plugins to the latest version the app is finally working again as it should.
However, I have noticed one very annoying difference:
With the old version when I ran the command:
cordova build android
it was compiling the app and installing it on the phone. However, it kept all the "data" from the previous version. So for example localStorage or SQLite database remained available.
When I run the same command under the new version, it replaces the app, removing all of it's "data".
As the app has a "setup process" I will now need to complete this every time I deploy a new version to the phone for testing, which is quite time consuming.
Is there any settings available to change this behavior?
I already checked the change log from Cordova but could not find any evidence what they have changed...
This issue was related to a bug in cordova, which got fixed with the latest release on March 2nd.
To fix it I did:
npm install -g cordova
cordova platform update android#5.1.1
details about the issue:
https://issues.apache.org/jira/browse/CB-10157
So in case you face a similar issue try to update your project - it worked just fine for me.
I have upgraded phonegap version to 2.2 but I checked the build is still 2.1 version. Will there be any issue in upgrade of the project and running the cloud build with the version 2.1
There might be some problems. If they changed anything on how the js calls native functions from version 2.1 to 2.2, wich I believe they did because of the changes on the plugins api, some functions that you might use on your app might not work on 1 or more platforms because of the version difference.
Basically, you would be making calls from the 2.2 js version that the 2.1 native version might not understand. You might need to wait for the update on the cloud build, or revert your project back to 2.1.