[CP Staging] chore: bump netinfo to newest version #34491

WoLewicki · 2024-01-15T10:33:30Z

Details

Quick fix with bumping the react-native-netinfo version which should resolve issue mentioned here: #31558 (comment)

Fixed Issues

#31558 (comment)

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

Pre-requisites: stable network

Open the app
Go to any report
Refresh app
Verify that offline indicator doesn't show below composer
Logout
Refresh app
Verify that offline indicator doesn't show below sign in button

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (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 not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
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
I verified that if a function's arguments changed that all usages have also been updated correctly
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(theme.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 that Avatar 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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 the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2024-01-15T10:34:05Z

@youssef-lr Please 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]

situchan · 2024-01-15T10:35:33Z

ios/Podfile.lock

    - React
  - OpenSSL-Universal (1.1.1100)
-  - Plaid (4.7.0)
+  - Plaid (4.7.1)


what's this for?

Idk why it appeared here but i just run pod install so maybe someone else didn't do it even though he should have.

I also run locally but still 4.7.0

Did you remove previous Podfile.lock? I do it to be sure that it is always up to date.

4.7.0 is the correct version
https://github.com/plaid/react-native-plaid-link-sdk/releases/tag/v10.8.0

Did you remove previous Podfile.lock? I do it to be sure that it is always up to date.

No. We should not remove previous lock file before pod install. Can you undo this change?

Yeah, but it has ~>: https://github.com/plaid/react-native-plaid-link-sdk/blob/23c5b8c2dcbdfe9532e70e4f92f1ef8b53da8b26/react-native-plaid-link-sdk.podspec#L19 which means it includes 4.7.1 if it was released. Or am I missing something?

I hope there will be no regression in that minor version update but let's consider out of scope for now.
We don't remove lock files when install npm, pod. So 4.7.0 should be correct

situchan · 2024-01-15T11:00:40Z

ios/Podfile.lock

  onfido-react-native-sdk: b346a620af5669f9fecb6dc3052314a35a94ad9f
  OpenSSL-Universal: ebc357f1e6bc71fa463ccb2fe676756aff50e88c
-  Plaid: 431ef9be5314a1345efb451bc5e6b067bfb3b4c6
+  Plaid: 4f7d68d53f9f8e4c74031ce8ba0f72dd88893d39


revert this as well

Ok reverted but now yoga checksum has been bumped for some reason. But since it has no version bump, it shouldn't change anything imo.

situchan · 2024-01-15T11:16:02Z

Tests/QA Step:

Pre-requisites: stable network

Open the app
Go to any report
Refresh app
Verify that offline indicator doesn't show below composer
Logout
Refresh app
Verify that offline indicator doesn't show below sign in button

situchan · 2024-01-15T11:22:21Z

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 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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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
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 using Avatar 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. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- 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(theme.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 that Avatar 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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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 the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

msafari.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

melvin-bot · 2024-01-15T11:23:42Z

🎯 @situchan, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #34492.

situchan · 2024-01-15T11:24:01Z

Tests/QA Step:

Pre-requisites: stable network

Open the app

Go to any report

Refresh app

Verify that offline indicator doesn't show below composer

Logout

Refresh app

Verify that offline indicator doesn't show below sign in button

Please add this to Tests/QA Steps

situchan · 2024-01-15T11:24:48Z

@youssef-lr let's merge asap so that no need to CP. Deploy is about to be happening soon 🚀

situchan · 2024-01-15T11:30:26Z

@mountiny can you please merge this so we don't need to CP?

mountiny

Thanks for a quick Pr, we have deployed now so I will CP this

OSBotify · 2024-01-15T12:26:42Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

…tinfo [CP Staging] chore: bump netinfo to newest version (cherry picked from commit e93f87d)

OSBotify · 2024-01-15T13:11:43Z

🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.25-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2024-01-15T13:41:17Z

🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.25-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2024-01-17T01:16:13Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.25-10 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

chore: bump netinfo to newest version

72ee346

WoLewicki requested a review from a team as a code owner January 15, 2024 10:33

melvin-bot bot requested review from youssef-lr and removed request for a team January 15, 2024 10:34

WoLewicki mentioned this pull request Jan 15, 2024

chore: Update React Native to 0.73.2 #31558

Merged

50 tasks

situchan reviewed Jan 15, 2024

View reviewed changes

fix: remove unnecessary Podfile.lock update

305c305

situchan approved these changes Jan 15, 2024

View reviewed changes

melvin-bot bot mentioned this pull request Jan 15, 2024

[HOLD for PAYMENT 2024-01-22] Payment issue for E/App PR#34491 #34492

Closed

mountiny assigned WoLewicki Jan 15, 2024

mountiny changed the title ~~chore: bump netinfo to newest version~~ [CP Staging] chore: bump netinfo to newest version Jan 15, 2024

mountiny approved these changes Jan 15, 2024

View reviewed changes

mountiny merged commit e93f87d into Expensify:main Jan 15, 2024

OSBotify pushed a commit that referenced this pull request Jan 15, 2024

Merge pull request #34491 from software-mansion-labs/@swm/fix-bump-ne…

c0a7450

…tinfo [CP Staging] chore: bump netinfo to newest version (cherry picked from commit e93f87d)

github-actions bot mentioned this pull request Jan 15, 2024

Deploy Checklist: New Expensify 2024-01-15 #34493

Closed

83 tasks

[CP Staging] chore: bump netinfo to newest version #34491

[CP Staging] chore: bump netinfo to newest version #34491

Uh oh!

Conversation

WoLewicki commented Jan 15, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 15, 2024

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

WoLewicki Jan 15, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

situchan commented Jan 15, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Tests/QA Step:

Uh oh!

situchan commented Jan 15, 2024

Reviewer Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 15, 2024

Uh oh!

situchan commented Jan 15, 2024

Tests/QA Step:

Uh oh!

situchan commented Jan 15, 2024

Uh oh!

situchan commented Jan 15, 2024

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Jan 15, 2024

Uh oh!

OSBotify commented Jan 15, 2024

Uh oh!

OSBotify commented Jan 15, 2024

Uh oh!

OSBotify commented Jan 17, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

WoLewicki commented Jan 15, 2024 •

edited

Loading

WoLewicki Jan 15, 2024 •

edited

Loading

situchan commented Jan 15, 2024 •

edited

Loading