-
Notifications
You must be signed in to change notification settings - Fork 168
Update to react-native 0.64 #1159
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
Conversation
…converted between string and number. Picker requires strings, but the target borderWidth value is a number.
…tiveSyntheticEvent. To compensate for its absence, make SyntheticEvent.dispatchConfig optional.
} | ||
} | ||
accessible={true} | ||
collapsable={false} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: check it we should enable this prop for performance gains. I vaguely recall this might do something similar to compose, where less views are in the render tree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, also similar to react fragments
Looks like 5.0.2 was only for cli-platform-ios, and once I forced that version using a resolution, things started working on my dev machine. Thank you for the pointer! I was going crazy trying to understand this. I don't know why they didn't do a 5.0.2 release of the entire CLI. |
Turns out I wasn't running the right command and didn't see that the failure still occurred. Then I took a closer look at yarn.lock and saw that cli-platform-ios was already 5.0.2 even though CLI was 5.0.1. I tried forcing the CLI ^6.0.0 and that still doesn't resolve it. So this hasn't actually been fixed in the CLI, in 5.x or 6.x. |
@afoxman Did some testing locally for win32, things seem to look good. At some point we probably want to bump the build of rex to a build that includes the changes to office to go to 0.64, but that can be its own PR. |
@tido64 FYI it seems your CLI fix didn't make it into later releases =/ |
Is |
@afoxman worked around it by copying the fix RNTA had to the iOS test app (which as I type, just realized is what running The reason for tagging you was simply to say "cli-platform-ios v 5.0.2" (which has your fix) isn't included in either the 5.x or 6.x release of "@react-native-community/cli" |
The fix I did was in I did manage to
We should probably remove Edit: In general, you should add the packages you want to link as dependencies (or devDependencies) and autolink will pick them up. |
Good callout on removing slider & SVG, since those are direct dependencies and can get autolinked. I can look into that separately since that doesn't seem to be blocking (Having issues filing an issue with GitHub to track right now). Interestingly enough, |
Also tagging @lenahong who I think is most recently involved with FURN Android stuff. This PR has the Android CI failing, and I'm still not sure why. |
I was able to make this pass locally by changing ReactNativeSlider_minSdkVersion=21 // was 16 I don't know enough Gradle yet to understand if/how I can change this from the android app. |
Can you try setting diff --git a/apps/android/src/build.gradle b/apps/android/src/build.gradle
index c9a77b9e..45595823 100644
--- a/apps/android/src/build.gradle
+++ b/apps/android/src/build.gradle
@@ -28,3 +28,6 @@ allprojects {
jcenter()
}
}
+ext {
+ minSdkVersion = 21
+} We should also align on the Flipper version that works with 0.64: diff --git a/apps/android/src/gradle.properties b/apps/android/src/gradle.properties
index 1bbc8cc2..d21d03f2 100644
--- a/apps/android/src/gradle.properties
+++ b/apps/android/src/gradle.properties
@@ -25,4 +25,4 @@ android.useAndroidX=true
android.enableJetifier=true
# Version of flipper SDK to use with React Native
-FLIPPER_VERSION=0.33.1
+FLIPPER_VERSION=0.75.1 Edit: |
Thanks! I tried this, and got a gradle error:
|
That's odd. I tested this locally and it works. Can you try bumping to latest react-native-test-app instead? |
Updating RNTA fixed it locally so I've pushed the change. CI runs things a bit differently - not easy to match/reproduce, which is a problem in itself, so I'll keep an eye on it. |
Platforms Impacted
Description of changes
Update all packages to react-native 0.64. This requires that a number of related dependencies be updated as well, such as react-native-windows, react-native-macos, @office-iss/react-native-win32, react, several @types packages, etc.
I also added resolutions to force the use of Metro 0.66.2 or later, as that is required for certain @rnx-kit package updates. Metro 0.66.2 is compatible with react-native 0.64.
Verification
I ran a CI build locally, which ran automated tests and bundling. I will also run the tester app manually and inspect the UI.
Pull request checklist
This PR has considered (when applicable):