-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock React version to ~18.2.0 #1148
Conversation
React 19 and React 18.3 are out (https://react.dev/blog/2024/04/25/react-19-upgrade-guide#react-18-3), but the React Native ecosystem is still on React 18.2. We need to lock the versions down until the React Native packages update.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1148 +/- ##
=======================================
Coverage 27.32% 27.32%
=======================================
Files 113 113
Lines 4816 4816
Branches 1037 1037
=======================================
Hits 1316 1316
- Misses 3498 3500 +2
+ Partials 2 0 -2
Flags with carried forward coverage won't be shown. Click here to find out more. |
I fixed the error from #1143 (comment), but the |
@shankari Any ideas? I fixed the React dependency issue, but CI still failed on both I was able to build Android locally |
The iOS failure is because the default iOS has been upgraded to 15, so unrelated to this
|
The android error is
according to https://stackoverflow.com/questions/68597899/bug-exception-in-phase-semantic-analysis-in-source-unit-buildscript-unsup, this is due to an incompatible java version |
I think all these failures are because the github runners were recently upgraded and we hadn't locked down all the versions, or the way that we locked down the versions failed. For android, we do attempt to lock down the version
but apparently it didn't work
I wonder if the GitHub runners have removed Java 11 |
iOS is now using the correct version but is broken
This is the same issue Falling back even further to 14.1, which i know works. For the android issue, maybe I need to change the |
Consistent with e-mission#1148 (comment)
Before this, we set only the `JAVA_HOME` to pin the java version This was working until a couple of days ago, when, even after setting the version, the java version was not changed. This may be due to the location for the java executable changing, so let's try to set the PATH as well Also print out several environment variables to help debug further Related info: e-mission#1148 (comment) e-mission#1148 (comment)
Failure on android seems to be because this is now an ARM machine. So instead of using
The error in iOS seems to be because
But it should be around: Let's check the version of the image that we are using... |
Ah, we currently specify
But
So let's just use xcode 13 for now, at least in this PR for iOS and then fix it while fixing e-mission/e-mission-docs#1060 For android, let's try to keep the most latest mac, but switch the environment variable |
…ctions runner Related context: e-mission#1148 (comment)
To be consistent with e-mission#1148 (comment) Before we fix e-mission/e-mission-docs#1060
This does fall back to android 11, but we still get a failure
Let's downgrade this to xcode 13 as well and confirm that it is fixed |
Consistent with e-mission#1148 (comment) and e-mission@b5072f3 (for iOS)
So this was all about the mac version. 0d0b212
Note that we still get the gradle warning but no error, and then we actually fix the gradle warning.
|
since pinning to OSX-13 fixed it e-mission#1148 (comment)
Because apparently the default version, even on the OSX 13 runner, is now xcode 15 e-mission#1148 (comment)
using macos 13 is not enough since the default xcode has changed. We do still need to pin xcode
|
Now, everything passed except for the code coverage. I know it has worked in the past, so will try to rerun in a bit |
Yay! Everything is finally passing with minimal changes. |
@JGreenlee @shankari Thanks for taking care of the issue |
React 19 and React 18.3 are out (https://react.dev/blog/2024/04/25/react-19-upgrade-guide#react-18-3), but the React Native ecosystem is still on React 18.2. We need to lock the versions down until the React Native packages update.