Skip to content
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

Upgrade to RN 0.64.0 #3430

Merged
merged 80 commits into from
Jun 16, 2021
Merged

Upgrade to RN 0.64.0 #3430

merged 80 commits into from
Jun 16, 2021

Conversation

cameronvoell
Copy link
Contributor

@cameronvoell cameronvoell commented Apr 29, 2021

Description

Upgrade React Native to version 0.64.0 (See RN Upgrade Helper)

Related PRs:

How has this been tested?

To test: Gutenberg Editor should work as expected.
Try to run all the manual tests.

Remaining Tasks:

  • rnmobile/try/upgrade-0-64 branch is updated to 0.64.0-rc3 and needs to be updated to 0.64.0 stable.
  • rnmobile/try/upgrade-0-64 needs to be updated with latest gutenberg trunk which contains some larger updates for handling WPAndroid composite builds
  • iOS Demo App needs to be fixed on rnmobile/try/upgrade-0-64
  • Need to create relevant PRs in other Repos following model of Upgrade React Native to 0.63 #2580
  • Check CI across all repos and address any issues

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented May 7, 2021

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

@cameronvoell cameronvoell requested a review from ceyhun May 14, 2021 06:01
@cameronvoell
Copy link
Contributor Author

Looks like npm run bundle command currently fails with error:

sh: ./gutenberg/node_modules/hermes-engine/osx-bin/hermes: No such file or directory

commenting here to bookmark solutions from this thread: facebook/react-native#28126

cameronvoell and others added 20 commits May 17, 2021 15:44
Expecting this to fix the following error:
```
/home/circleci/project/gutenberg/node_modules/@react-native/polyfills/error-guard.js:14
type ErrorHandler = (error: mixed, isFatal: boolean) => void;
        ^^^^^^^^^^^^

SyntaxError: Unexpected identifier

    at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
    at Object.<anonymous> (gutenberg/node_modules/react-native/jest/setup.js:434:6)
```
@hypest hypest removed this from the 1.55.0 (17.6) milestone Jun 11, 2021
Copy link
Contributor

@hypest hypest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I haven't gone into a detailed review (line by line) that I'd normally do and instead trust the many people that have already worked on this, plus the green CI and tests, including the writing flow tests (myself and @SiobhyB on iOS) successes.

"name": "react-native-blur",
"version": "0.8.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is strange 😕 We probably won't want this kind of downgrade. I'll check the diff of native iOS files and react-native-blur's podspec.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be wrong in the Podspec, we'll need to fork this repo:
https://github.com/Kureev/react-native-blur/blob/v3.3.0/react-native-blur.podspec#L3

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hypest I've created the fork and pushed the related fix: wordpress-mobile/react-native-blur#1, but I may need some help with setting up Jitpack :(

After it's set up, will push a v3.6.1-wp tag in wp-fork branch to get it used in the generated podspecs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the ping Ceyhun! We had the chance to talk about this (the new fork) during a 1:1 and we said that it's fine for us to not depend on the fork for the initial merge of the RN upgrade, and wrangle it afterwards as part of cleaning up all the fork upgrade PRs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just added a workaround for now in generate-podspecs.sh for react-native-blur specifically and also some warning messages to catch this and also to not modify podspecs manually.

@hypest
Copy link
Contributor

hypest commented Jun 15, 2021

Test iOS on Device - Full was failing with [quit()] Unexpected data in simpleCallback. which is something we've seen happening outside this PR anyway so, went ahead and restarted the failed CI job.

"homepage": "https://github.com/react-native-community/react-native-blur",
"source": {
"git": "https://github.com/react-native-community/react-native-blur.git"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also no tag or commit is defined in the latest version: https://github.com/Kureev/react-native-blur/blob/v3.6.1/react-native-blur.podspec#L15, which means this would depend on main branch instead.

And even if it was defined, it's still not published on npm: https://www.npmjs.com/package/@react-native-community/blur/v/3.6.1

@hypest
Copy link
Contributor

hypest commented Jun 16, 2021

The "Publish to S3" job on 084cf3d seemed to fail due to some networking issue, most possibly. Let's just restart when all jobs conclude.

@ceyhun ceyhun enabled auto-merge June 16, 2021 18:09
@ceyhun ceyhun merged commit 1130aa6 into develop Jun 16, 2021
@ceyhun ceyhun deleted the try/upgrade-0-64 branch June 16, 2021 18:53
@fluiddot fluiddot added this to the 1.56.0 (17.7) milestone Jul 2, 2021
@fluiddot fluiddot mentioned this pull request Jul 2, 2021
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants