-
Notifications
You must be signed in to change notification settings - Fork 3k
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 the react native dependency to v0.71.2-alpha.3 #15130
Upgrade the react native dependency to v0.71.2-alpha.3 #15130
Conversation
@priyeshshah11 If PR is ready for review please link the issue correctly in the PR description before submitting |
It is not ready, thus in draft. Will check the linking. |
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.
Per this issue we should be able to remove this jest preset as part of this PR
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.
We've now published v0.71.2-alpha.2
, so this PR should be updated to use that release instead
@abdulrahuman5196 Could you please try building & testing this PR? |
…s. Also upgraded react-native-image-picker & react-native-plaid-link-sdk
task copyDownloadableDepsToLibs(type: Copy) { | ||
from configurations.implementation | ||
into 'libs' | ||
implementation("androidx.lifecycle:lifecycle-viewmodel-ktx:2.4.0") |
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.
added this line due to this error & SO answer https://stackoverflow.com/a/69923303/16762514
@@ -81,12 +81,12 @@ | |||
"onfido-sdk-ui": "10.3.0", | |||
"process": "^0.11.10", | |||
"prop-types": "^15.7.2", | |||
"pusher-js": "^7.0.6", | |||
"react": "18.1.0", | |||
"pusher-js": "7.4.0", |
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.
upgraded pusher because of this issue pusher/pusher-js#654 (comment)
package.json
Outdated
"react-native-pdf": "^6.6.2", | ||
"react-native-performance": "^4.0.0", | ||
"react-native-permissions": "^3.0.1", | ||
"react-native-picker-select": "git+https://github.com/Expensify/react-native-picker-select.git#77cc9d42c474a693755941b10ee4c2d6f50e5346", | ||
"react-native-plaid-link-sdk": "^7.2.0", | ||
"react-native-quick-sqlite": "^5.0.3", | ||
"react-native-plaid-link-sdk": "https://github.com/Pedroor/react-native-plaid-link-sdk.git", |
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.
Waiting on this PR plaid/react-native-plaid-link-sdk#518 to be merged
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.
@mountiny FYI, still waiting on this.
@mountiny @Santhosh-Sellavel One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
I was able to fix the iOS build issues with @abdulrahuman5196's help & had to update a few more libs to fix android. Now all platforms are building & working but with a few issues, @abdulrahuman5196 It is now ready for you to test. @mountiny & @roryabraham We should now add the Some issues that I am aware of & will look into later are:
|
@priyeshshah11 Thank you. Will start testing from my end. Just to note:
I remember seeing this issue before this PR as well, not sure though have to double check. I think its best to not include issues which is not related to this PR. I am just being cautious not to cause any regression. Correct me if wrong. |
@abdulrahuman5196 How did the testing go? I have left the testing items in the PR description for you & I think the reviewer checklist is for C+ to use. |
Working on testing. Will complete by tomorrow. I will copy paste the PR description then and work on it as I can't edit it directly. |
Feel free to send it to me so I can edit in the og description as well |
Note: Will copy paste to PR description once all checklist is tested DetailsUpgrade the react native dependency to v0.71.2-alpha.1 Fixed Issues$ #15124 Tests
Offline testsQA Steps
PR Author Checklist
Screenshots/VideosWebMobile Web - ChromeMobile Web - SafariDesktopdesktop.1.mp4desktop.new.2.mp4desktop.new.3.mp4desktop.new.4.mp4desktop.new.5.mp4desktop.new.6.mp4desktop.new.7.mp4iOSios.1.mp4ios.2.mp4ios.3.mp4ios.4.mp4ios.5.mp4ios.6.mp4Android |
@priyeshshah11 I am facing issues building ios project with the latest commit(Attached the screenshot of the issue). I think its related to this plaid version in the PR - "react-native-plaid-link-sdk": "^7.2.0",
+ "react-native-plaid-link-sdk": "https://github.com/Pedroor/react-native-plaid-link-sdk.git", |
sure, will do once PR is up-to-date with main |
🧪🧪 Use the links below to test this build in android and iOS. Happy testing! 🧪🧪 |
…eshshah11-upgrade-rn-version
@mountiny @aimane-chnaif resolved conflicts, will be offline today as will be on a flight. |
I tested this android release build and confirmed pill multiline issue not happening. |
@aimane-chnaif Thanks I think once you get the reviewer checklist in, we can merge this! |
@priyeshshah11 please fill checklist. If not applicable, just check them off. |
@aimane-chnaif went ahead and did it given Priyesh might be travelling |
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.
Reviewer Checklist
- I have verified the author checklist is complete (all boxes are checked off).
- I verified the correct issue is linked in the
### Fixed Issues
section above - I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the
Tests
section - I verified the steps for Staging and/or Production testing are in the
QA steps
section - I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I verified the steps for local testing are in the
- I checked that screenshots or videos are included for tests on all platforms
- I included screenshots or videos for tests on all platforms
- I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
- If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
- I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
toggleReport
and notonIconClick
). - I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to
src/languages/*
files and using the translation method - I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is correct English and approved by marketing by adding the
Waiting for Copy
label for a copy review on the original GH to get the correct copy. - I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in
STYLE.md
) were followed
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e.
- If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- I verified that this PR follows the guidelines as stated in the Review Guidelines
- I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like
Avatar
, I verified the components usingAvatar
have been tested & I retested again) - I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a
/** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
) - All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
- If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e.
StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)
- If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
- If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like
Avatar
is modified, I verified thatAvatar
is working as expected in all cases) - If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
- If a new page is added, I verified it's using the
ScrollView
component to make it scrollable when more elements are added to the page. - If the
main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
Screenshots/Videos
Web
Mobile Web - Chrome
Mobile Web - Safari
Desktop
iOS
Android
Latest version tests well.
There are some console errors but checking off since they're handled in follow-up issue
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.
Great, I think I would go ahead and merge this what do you think @roryabraham
I think we can just go ahead and |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/mountiny in version: 1.2.99-0 🚀
|
Thanks! 🙌 @mountiny |
🚀 Deployed to production by https://github.com/francoisl in version: 1.2.99-6 🚀
|
Details
Updating the react native version to 0.71 :shiny:
Fixed Issues
$ #15124
PROPOSAL: #15124 (comment)
Tests
Full regression test
Offline tests
Nothing specific
QA Steps
Full regression test
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.Screenshots/Videos
Web
Mobile Web - Chrome
Mobile Web - Safari
Desktop
iOS
Android