fix offline indicator not show in mobile

[hungvu193]

Details

Fix offline indicator not show in mobile

Fixed Issues

$ #23165
PROPOSAL: #23165 (comment)

Tests

1. Login with any account
2. Turn off the internet connection (or enable force offline in Preferences).
3. Go to Profile => Click user photo => upload photo => choose any photo.
4. Verify there's OfflineIndicator at bottom.
5. Go to Profile => Personal Details => Date of Birth => Click on the year => YearPickModal will show up.
6. Verify there's OfflineIndicator at bottom.
7. Go to Profile => Personal Details => Home Address => Click on the Country filed => CountrySelectorModal will show up.
8. Verify there's OfflineIndicator at bottom.
9. Go to Profile => Personal Details => Home Address => Click on the State filed => StateSelectorModal will show up.
10. Verify there's OfflineIndicator at bottom.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Login with any account
2. Turn off the internet connection (or enable force offline in Preferences).
3. Go to Profile => Click user photo => upload photo => choose any photo.
4. Verify there's OfflineIndicator at bottom.
5. Go to Profile => Personal Details => Date of Birth => Click on the year => YearPickModal will show up.
6. Verify there's OfflineIndicator at bottom.
7. Go to Profile => Personal Details => Home Address => Click on the Country filed => CountrySelectorModal will show up.
8. Verify there's OfflineIndicator at bottom.
9. Go to Profile => Personal Details => Home Address => Click on the State filed => StateSelectorModal will show up.
10. Verify there's OfflineIndicator at bottom.

• 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 / Chrome
  • iOS / native
  • iOS / 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 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
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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(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 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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

hfaz.mov

Mobile Web - Chrome

1080.mov

Mobile Web - Safari

477.mov

Desktop

hfaz.mov

iOS

Android

1080.mov

[melvin-bot]

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

[melvin-bot]

@shawnborton @eVoloshchak 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]

[hungvu193]

@eVoloshchak PR is ready for review. Please have a look, ty 😄

[eVoloshchak]

@hungvu193, can we just wrap BaseModal with the screen wrapper? That would add offline indicator to all the modals

[hungvu193]

@eVoloshchak I don't think we should, BaseModal is also being used for ConfirmModal as well, that's being said, if we wrapped it with ScreenWrapper, we can also see the OfflineIndicator at the bottom of it.
The best way to do that is wrapping ScreenWrapper with any modal that's full screen modal.

[eVoloshchak]

The best way to do that is wrapping ScreenWrapper with any modal that's full screen modal

Is there a way we could detect that? The current approach is also fine, but I'm wondering if we could have a more universal solution

[hungvu193]

I think we can update the document, every time we create a new full screen modal, we should wrap their content inside ScreenWrapper like we're doing that with our normal screens. There are only few full screen modals in our app, so I think the current approach is just fine.

[eVoloshchak]

Repeat steps above with CountrySelectorModal, YearPickerModal and StateSelectorModal.

@hungvu193, QA team members aren't developers, they might not know where those components are used and how to get to them.
It's better to overexplain the tests, let's just have similar sections for all the modals

Login with any account
Go to ... => Click ... => ...
Turn off the internet connection.
Verify there's "You appear to be offline" text at the bottom

[hungvu193]

Repeat steps above with CountrySelectorModal, YearPickerModal and StateSelectorModal.

@hungvu193, QA team members aren't developers, they might not know where those components are used and how to get to them. It's better to overexplain the tests, let's just have similar sections for all the modals

Login with any account
Go to ... => Click ... => ...
Turn off the internet connection.
Verify there's "You appear to be offline" text at the bottom

Thanks for reminding me @eVoloshchak 👍 . Updated the steps

[sakluger]

@hungvu193 there's a related issue where the offline indicator is not showing on the Profile > Personal Details > Country & State screen (GH issue). Do you know if they are the same root cause and will this PR fix that issue as well?

[hungvu193]

@hungvu193 there's a related issue where the offline indicator is not showing on the Profile > Personal Details > Country & State screen (GH issue). Do you know if they are the same root cause and will this PR fix that issue as well?

@sakluger yes. This pr fixed it as well

[eVoloshchak]

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 / 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 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(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 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 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

Web

Screen.Recording.2023-08-10.at.18.41.51.mov

Mobile Web - Chrome

screen-20230810-184505.mp4

Mobile Web - Safari

Screen.Recording.2023-08-10.at.19.07.51.mov

Desktop

Screen.Recording.2023-08-10.at.19.10.49.mov

iOS

Screen.Recording.2023-08-10.at.19.09.20.mov

Android

screen-20230810-190242.mp4

[eVoloshchak]

@hungvu193, could you resolve the conflicts please?

[hungvu193]

@hungvu193, could you resolve the conflicts please?

Sure, resolving now...

[eVoloshchak]

• There's also a typo in Fixed Issues section, the first link is incorrect, it should just point to [HOLD for payment 2023-08-24] [$1000] Profile - OfflineIndicator doesn't appear on AvatarCrop Modal. #23165

• Steps should specify that offline indicator is visible on modals only on mobile interface

[hungvu193]

• There's also a typo in Fixed Issues section, the first link is incorrect, it should just point to [$1000] Profile - OfflineIndicator doesn't appear on AvatarCrop Modal. #23165
• Steps should specify that offline indicator is visible on modals only on mobile interface

Oh thank you, updated it as well!

[eVoloshchak]

I think this was a merge that went wrong, we shouldn't change this file here😅

[hungvu193]

yeah, right. Let me reset it 😂

[hungvu193]

updated!

[OSBotify]

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

[OSBotify]

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.3.54-0 🚀

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

[OSBotify]

🚀 Deployed to staging by https://github.com/arosiclair in version: 1.3.54-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.54-13 🚀

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