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

[Update Account Settings] Preferences, About, Security #35672

Conversation

kosmydel
Copy link
Contributor

@kosmydel kosmydel commented Feb 2, 2024

Details

Update all pages in AccountSettings that use illustrations according to the new designs:

  • Preferences,
  • Security,
  • About.

It also this minor regression.

And it also adds missing icons in the Account Settings.

Fixed Issues

$ #35606
$ #35607
$ #35608
$ #35905
$ #36246
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console
  • Go to Account Settings and verify.
    • Preferences Page
    • Security Page
    • About Page
    • Link icons on the LHN menu (Help & Go to Expensify Classic).
  • Verify the new designs.
  • Verify the translations (Spanish and English).

Offline tests

N/A

QA Steps

  • Verify that no errors appear in the JS console
  • Tests from above

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 Screenshot 2024-02-08 at 13 31 03 Screenshot 2024-02-08 at 11 09 55 Screenshot 2024-02-08 at 13 31 13
Android: mWeb Chrome Screenshot 2024-02-08 at 11 02 04 Screenshot 2024-02-08 at 13 32 48 Screenshot 2024-02-08 at 13 32 57
iOS: Native

simulator_screenshot_7E45C5B7-1B1C-4A86-81FE-6F3D4AFEEDB5

simulator_screenshot_ED8AD3D3-CE0A-4B39-A511-FC2138B414B9

simulator_screenshot_10E8A427-D5F1-457C-BA27-1873D8CBE89A

iOS: mWeb Safari

simulator_screenshot_81C64E26-FDA9-4D44-978E-5E3AFF4C6F6A

simulator_screenshot_859F248E-65E6-4312-9E0C-9A21701E98C0

simulator_screenshot_67B99887-3A09-41AC-A015-DF20ECF5D3A9

MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@kosmydel kosmydel changed the title Update account settings/preferences [Update Account Settings] Preferences Feb 2, 2024
src/languages/en.ts Outdated Show resolved Hide resolved
@kosmydel
Copy link
Contributor Author

kosmydel commented Feb 8, 2024

The PR is ready for review.


However, I found one issue with StatusBar:

The StatusBar is not updating after the theme is changed. Previously it worked, because we didn't have to change the status bar color when changing the theme (both light and dark themes used the blue status bar color to match the illustration background). Now, as the illustration is no longer stuck to the header, we need to switch the colors of the status bar, which apparently doesn't work.

I can see that there are some other issues related to StatusBar, maybe someone who worked with this component closer could have a look?
cc @hayata-suenaga, @mountiny

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-02-08.at.11.16.48.mp4

@kosmydel kosmydel changed the title [Update Account Settings] Preferences [Update Account Settings] Preferences, About, Security Feb 8, 2024
@kosmydel
Copy link
Contributor Author

kosmydel commented Feb 9, 2024

@kosmydel This #35672 (comment) has not been addressed

0375e27

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Thanks for thorough testing, moving this ahead

@@ -26,6 +27,7 @@ const DotLottieAnimations: Record<string, DotLottieAnimation> = {
file: require('@assets/animations/PreferencesDJ.lottie'),
w: 375,
h: 240,
backgroundColor: colors.blue500,
Copy link
Contributor

Choose a reason for hiding this comment

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

I tmight be nice to add this as a follow up but I would say once we will need this dynamic which we dont right now as far as I know

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

SignInPage tests need to be updated to mock the Navigation correctly after the updateStatusBarStyle change

@ishpaul777
Copy link
Contributor

ishpaul777 commented Feb 11, 2024

Changes Suggested to resolve the Statusbar background color issue (not adding proposal because new changes needed are straightforward i belive can be done in the PR)

Remove these

[SCREENS.HOME]: {
backgroundColor: colors.productLight200,
statusBarStyle: CONST.STATUS_BAR_STYLE.DARK_CONTENT,
},

[SCREENS.HOME]: {
backgroundColor: colors.productDark200,
statusBarStyle: CONST.STATUS_BAR_STYLE.LIGHT_CONTENT,
},

and adding this (for sign in page status bar)

[NAVIGATORS.BOTTOM_TAB_NAVIGATOR]: {
        backgroundColor: colors.productDark200,
        statusBarStyle: CONST.STATUS_BAR_STYLE.DARK_CONTENT,
}

and merging #34409 which solves #35672 (comment), #35672 (comment) and minor suggestions from Rory #34154 (comment)

Currently, the home screen has also wrong status bar color, but changing it breaks the insets on android.

Refreshing preference page on mWeb does not have correct status bar color

@kosmydel
Copy link
Contributor Author

The performance tests are fixed. cc @mountiny

mountiny
mountiny previously approved these changes Feb 12, 2024
Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Thank you

@mountiny
Copy link
Contributor

Sorry for not getting to this sooner, please ping me in slack once you resolve conflicts

@filip-solecki
Copy link
Contributor

@mountiny conflicts resolved

@kosmydel
Copy link
Contributor Author

kosmydel commented Feb 13, 2024

Changes Suggested to resolve the Statusbar background color issue (not adding proposal because new changes needed are straightforward i belive can be done in the PR)

@ishpaul777 I believe that this is out of the scope of this original issue. If we have dedicated PR (#34409) for handling the StatusBar we should focus on fixing all related issues there.

@kosmydel
Copy link
Contributor Author

Some PR introduced "Mute all sounds from Expensify" switch. Can someone confirm if it looks ok? The Figma designs doesn't cover this case. If needed, please update the designs.

cc @shawnborton , @trjExpensify , @dubielzyk-expensify , @mountiny

Screenshot 2024-02-13 at 10 52 14

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

That looks good thank you

@mountiny mountiny merged commit 4f1521c into Expensify:main Feb 13, 2024
16 checks passed
@OSBotify
Copy link
Contributor

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

@@ -105,7 +105,7 @@ const lightTheme = {
statusBarStyle: CONST.STATUS_BAR_STYLE.LIGHT_CONTENT,
},
[SCREENS.SETTINGS.PREFERENCES.ROOT]: {
backgroundColor: colors.blue500,
backgroundColor: colors.productLight100,
statusBarStyle: CONST.STATUS_BAR_STYLE.LIGHT_CONTENT,
Copy link
Contributor

@ishpaul777 ishpaul777 Feb 13, 2024

Choose a reason for hiding this comment

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

this should be in dark mode i think

            statusBarStyle: CONST.STATUS_BAR_STYLE.DARK_CONTENT,
Screen.Recording.2024-02-14.at.4.08.20.AM.mov

@kosmydel

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed here

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/thienlnam in version: 1.4.41-12 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.