react-native: React-native version mismatch 0.59.4

Adding android:usesCleartextTraffic="true" to AndroidManifest.xml seems to fix the issue on my end.

After investigation, it seems this bug is appearing on all devices/emulators only on android 9. The app run successfully on android 8 (API 26/27) but mismatch on android 9 (API 28).

I update the react-native version: 0.57.4 to 0.59.8 and i getting the following message “React-Native Version Mismatch”

This solution works for me:

1.- In the folder of the project, update all the code react-native in the Android Studio:

react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/

2.- Go to Android Studio and FILE->>INVALIDATE CACHES/RESTART 3.- In Android Studio, BUILD->>CLEAN PROJECT 4.- In Android Studio, BUILD->>REBUILD PROJECT 5.- Delete App in simulator or Devices 6.- Run… I hope to help you!

I just went through another battle with this, on Android: this time, the version mismatch box seemed to be caused by my having added main and debug network_security_config.xml files and referenced them from my main and debug AndroidManifest.xml files (our app needs to talk to S3 in cleartext, and developer host machines when developing against real devices). I banged my head against this for a while before deciding it was OK to get rid of both network_security_config.xml files and just added android:usesCleartextTraffic="true" to both manifests.

The thing that really bugs me about this problem is that I know that “Native version” always gives the react-native package version from my package.json, but I have no clue where the Javascript version is coming from - it’s 0.57.3, which I guess was the version we started with before upgrading RN, but there aren’t any references to it in my sources. And why should the message go away when I do network security configuration differently? (Please add comments if you can explain any of this!)

adding the missing “react-native”: “0.57.1” to app.json, (with sdk version set to 31), solved (at last) the problem in my case (expo client). (as displayed in https://stackoverflow.com/questions/53402555/expo-react-native-version-mismatch-error-javascript-version-0-55-4-native). (More generally, the right matching of those two versions seems thus to be a crucial point).

Hello, I work with Linoa65 and I took the tests a little further. I reset the phone on which the error was displayed and it turns out that even after that, it doesn’t work, we have the same error. I also tried to delete our project and re-clone it but it’s always the same. Computers have also been changed to change the project, but nothing is working.

If you are using expo, all you have to do is

sudo expo install react-native

I also had this problem, after upgrading from 0.55.3 to 0.59.8 using rn-diff-purge; it only happens on one Android 9 device, not on Android 9 simulators or an Android 8 device. None of the things that @Linoa65 tried worked for me either, nor did the android:usesCleartestTraffic="true" thing (and it’s already in my android/app/src/debug/AndroidManifest.xml, since that file was a change shown by rn-diff-purge during my upgrade).

I went back and reexamined each of the changes that rn-diff-purge had suggested, and realized that I’d missed three: I hadn’t updated the gradle-wrapper.jar or gradle-wrapper.properties, and also hadn’t added the new DEFAULT_JVM_OPTS values in the gradlew script. Fixing these things made the problem go away for me.

Hey everyone - thanks for opening this issue. It looks like there is something weird going on here, but I don’t know if it’s really a react-native “caused” issue; it seems to be related to some misconfiguration of complex project that went through an upgrade process.

This is also super weird:

After investigation, it seems this bug is appearing on all devices/emulators only on android 9. The app run successfully on android 8 (API 26/27) but mismatch on android 9 (API 28).

What @JKCooper2 said on top seems the right way to debug this:

Do a search inside of your yarn or npm lock file for 0.57.3 and see which library is using that version. I’ve had some issues with react-native-video installing its own version of react-native which conflicted, so I ended up running a postInstall script that would delete that folder from node_modules/react-native-video

And given that there has not being any feedback about it, I’d suggest you try to look at it closely at the .lock file again.

Maybe cleaning up all the caches could help?

rm -rf node_modules;
rm -rf $TMPDIR/react-native-packager-cache-*;
rm -rf $TMPDIR/metro-*;
rm -rf $TMPDIR/react-*;
rm -rf $TMPDIR/haste-*;
watchman watch-del-all;
yarn;
yarn start --reset-cache; (for bundler)

Also, please create a repro so that we can take a closer look at this issue, as it stands now there isn’t much we can do and because of that I’d close this if we don’t have one.