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

Delegate access: Add account switcher #47338

Merged
merged 101 commits into from
Aug 28, 2024

Conversation

rushatgabhane
Copy link
Member

@rushatgabhane rushatgabhane commented Aug 13, 2024

Details

Reference figma: https://www.figma.com/design/0hkXDnwqXN8J51MHEWQeLC/Account-Access-(Copilot)?node-id=1-3&t=lFirw8Aa0NwEygPW-0

Fixed Issues

$ #46920
$ #46921
PROPOSAL:

Tests

Profile picture

  1. Go to settings > Profile
  2. Verify that you can view profile photo, edit and upload a new one.

Share code

  1. Go to settings > Profile
  2. Click share
  3. Verify that share code page opens

Account switcher

  1. Enable the beta newDotCopilot
  2. Go to an account that can act as a copilot for multiple accounts. Or you can add them via oldDot by following instructions on help site.
  3. Click the account switcher
  4. Verify that a popover opens
  5. Verify that you can see all accounts you can act as a copilot
  6. Click an account
  7. Verify that you are logged in as that account now
  8. The app might crash after switching accounts. You can refresh to fix it.
  9. Click account switcher again
  10. Click your original account and verify that you can go back to your account

Offline test

  1. Go offline
  2. Switch accounts
  3. Verify that you see a popover saying you can't perform this action right now
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design 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 not building after upgrade

Android: mWeb Chrome
iOS: Native
Screen.Recording.2024-08-28.at.04.24.17.mov
Screen.Recording.2024-08-28.at.15.28.36.mov
iOS: mWeb Safari
Screen.Recording.2024-08-28.at.04.47.06.mov
Screen.Recording.2024-08-28.at.15.30.36.mov
MacOS: Chrome / Safari
Screen.Recording.2024-08-22.at.00.16.59.mov
Screen.Recording.2024-08-13.at.21.58.33.mov
image
MacOS: Desktop
Screen.Recording.2024-08-28.at.04.50.41.mov

@rushatgabhane
Copy link
Member Author

rushatgabhane commented Aug 28, 2024

Another issue is after some time, all API calls start returning code 407 session has expired. But the user is not signed out.

We have a request middleware that performs Reauthentication.

But the server never sends a new token, and the middleware never signs out the user. So the user will be stuck with app that is loading and will have to manually sign out.

const Reauthentication: Middleware = (response, request, isFromSequentialQueue) =>

@dangrous @parasharrajat this is a more global issue so I don't want to touch it 😅
We'll need clear reproduction steps, exact root cause and then a discussion on slack on how to handle this.

@rushatgabhane
Copy link
Member Author

IOS: BUG: While offline, Alert does not show up on changing accounts

fixed ✅

@rushatgabhane
Copy link
Member Author

@parasharrajat all yours!!! I'm confident on merging. Great work on finding all the bugs and reviewing the code

@dangrous
Copy link
Contributor

Another issue is after some time, all API calls start returning code 407 session has expired. But the user is not signed out.

We have a request middleware that performs Reauthentication.

But the server never sends a new token, and the middleware never signs out the user. So the user will be stuck with app that is loading and will have to manually sign out.

const Reauthentication: Middleware = (response, request, isFromSequentialQueue) =>

@dangrous @parasharrajat this is a more global issue so I don't want to touch it 😅 We'll need clear reproduction steps, exact root cause and then a discussion on slack on how to handle this.

For this one - do you think that's a backend issue? Like, do I need to look at how those Reauthenticate requests are processed on the backend? Or, should we see if we can log the user out if they get a 407 response? Either way I agree this can be handled later. (Roughly how long before you start getting those responses?)

@rushatgabhane
Copy link
Member Author

rushatgabhane commented Aug 28, 2024

Roughly how long before you start getting those responses

definitely more than 30 minutes

do you think that's a backend issue

On frontend, Reauth assumes that after N retries you will get the auth token in at least one of the requests.

But after switching accounts, reauth does not work on delegate account and not even after gou return back to your account.

Reauth is not possible from the backend itself as soon as the user has switched account or retuned back.

This will be mostly a frontend fix / few changes from backend to sign out

What do you think?

@dangrous
Copy link
Contributor

hm yeah if it's over 30 mins, let's handle that as polish. My guess is in the majority of cases 30 mins will be enough

@parasharrajat
Copy link
Member

parasharrajat commented Aug 28, 2024

@rushatgabhane There is another issue. When we switch accounts, some chat names change to Chat Report in LHN. I think it is not in the scope of this PR but noting it here.

29.08.2024_00.07.50_REC.mp4

@rushatgabhane
Copy link
Member Author

@parasharrajat can you attach a screenshot whenever you see it again? so we are on same page

@parasharrajat
Copy link
Member

parasharrajat commented Aug 28, 2024

Screenshots

🔲 iOS / native

29.08.2024_00.05.03_REC.mp4

🔲 iOS / Safari

29.08.2024_00.08.50_REC.mp4

🔲 MacOS / Desktop

28.08.2024_23.28.17_REC.mp4

🔲 MacOS / Chrome

28.08.2024_23.25.19_REC.mp4

🔲 Android / Chrome

29.08.2024_00.10.49_REC.mp4

🔲 Android / native

29.08.2024_00.06.19_REC.mp4

@parasharrajat
Copy link
Member

@rushatgabhane Updated the same comment #47338 (comment)

Copy link
Member

@parasharrajat parasharrajat left a 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 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.

🎀 👀 🎀 C+ reviewed

Copy link
Contributor

@dangrous dangrous left a comment

Choose a reason for hiding this comment

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

K, let's do it! It looks good to me, and I think we'll have plenty of time to handle additional issues that come up when we're finalizing the other PRs.

Thank you both so much for all the time you've put into this!

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.26-1 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.0.26-6 🚀

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

@dangrous dangrous mentioned this pull request Sep 4, 2024
50 tasks
const createBaseMenuItem = (personalDetails: PersonalDetails | undefined, error?: TranslationPaths, additionalProps: MenuItemWithLink = {}): MenuItemWithLink => {
return {
title: personalDetails?.displayName ?? personalDetails?.login,
description: personalDetails?.login,
Copy link
Contributor

Choose a reason for hiding this comment

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

Coming from #48648, we should have used Str.removeSMSDomain to ensure phone numbers are displayed correctly (without the @expensify.sms suffix).

const headlineSize = variables.fontSizeXLarge;
const spaceBetweenHeadlineAndLabel = styles.mt1.marginTop + (variables.lineHeightXXLarge - variables.fontSizeXLarge) / 2;
const labelSize = variables.fontSizeLabel;
const startPositionX = 30;
Copy link
Contributor

Choose a reason for hiding this comment

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

Using an absolute start position caused a mismatch between skeleton view and the loaded view. More details here. #49548

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.

9 participants