Skip to content

Remove passwordless beta logic #22461

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

Merged
merged 22 commits into from
Jul 21, 2023
Merged

Conversation

NikkiWines
Copy link
Contributor

@NikkiWines NikkiWines commented Jul 8, 2023

Details

Removes a lot of password-based code and passwordless beta logic that's no longer necessary now we've flipped everyone over

Fixed Issues

Part of https://github.com/Expensify/Expensify/issues/249398

PROPOSAL:

Tests

  1. Create a new account and validate it
  2. Log out of the account and log back in
  3. Navigate to Settings > Profile > Contact Method > New Contact Method
  4. Add a new contact method and validate it
  5. Navigate to Settings > Payments > Add Payment Method > Debit Card
  6. Add a new debit card and confirm you're not asked for a password
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

  1. Create a new account and validate it
  2. Log out of the account and log back in
  3. Navigate to Settings > Profile > Contact Method > New Contact Method
  4. Add a new contact method and validate it
  5. Navigate to Settings > Payments > Add Payment Method > Debit Card
  6. Add a new debit card and confirm you're not asked for a password
  • 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 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
newuser-contactmethod-web.mov
debitcard-web.mov
Mobile Web - Chrome
Mobile Web - Safari
Simulator.Screen.Recording.-.iPhone.14.-.2023-07-17.at.18.16.21.mp4
Desktop
desktop.mov
iOS
ios.mp4
Android
Screen.Recording.2023-07-18.at.10.55.31.mov

@NikkiWines NikkiWines self-assigned this Jul 8, 2023
@NikkiWines NikkiWines requested a review from johnmlee101 July 15, 2023 00:31
@NikkiWines
Copy link
Contributor Author

This should be good for review! Gonna add screenshots first thing Monday 🙇

@NikkiWines NikkiWines marked this pull request as ready for review July 15, 2023 01:33
@NikkiWines NikkiWines requested a review from a team as a code owner July 15, 2023 01:33
@melvin-bot melvin-bot bot requested review from srikarparsi and removed request for a team July 15, 2023 01:34
@melvin-bot
Copy link

melvin-bot bot commented Jul 15, 2023

@srikarparsi 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]

@NikkiWines
Copy link
Contributor Author

Did some testing today, will follow up with android tomorrow 🙇

Copy link
Contributor

@johnmlee101 johnmlee101 left a comment

Choose a reason for hiding this comment

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

updatePasswordAndSignin should be removed as well from Session/index.js, right?

@NikkiWines
Copy link
Contributor Author

updatePasswordAndSignin should be removed as well from Session/index.js, right?

Oops yes, and now I have conflicts 😢

@NikkiWines
Copy link
Contributor Author

@johnmlee101 updated!

@NikkiWines
Copy link
Contributor Author

Android mWeb is up but my android sim won't load newDot 😭

@NikkiWines
Copy link
Contributor Author

@srikarparsi @johnmlee101 friendly bump here just cause this one gets conflicts every day 😭

@johnmlee101
Copy link
Contributor

@srikarparsi will you be able to work on the checklist?

@johnmlee101
Copy link
Contributor

johnmlee101 commented Jul 20, 2023

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 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-07-21.at.4.29.52.PM.mov
Mobile Web - Chrome
Screen.Recording.2023-07-21.at.4.31.00.PM.mov
Mobile Web - Safari
Screen.Recording.2023-07-21.at.4.33.47.PM.mov
Desktop
DesktopRecording.mov
iOS
Screen.Recording.2023-07-21.at.4.52.02.PM.mov
Android
Screen.Recording.2023-07-21.at.4.57.39.PM.mov

@srikarparsi
Copy link
Contributor

Hey @johnmlee101! Yup, I can test on the other platforms and will add screenshots into your checklist

@srikarparsi
Copy link
Contributor

srikarparsi commented Jul 20, 2023

@NikkiWines Should I be on a specific branch of web when testing this PR. I'm getting the following error:

image

These are the logs:

2023-07-20T21:31:55.536618+00:00 expensidev2004 php-fpm: tAivwu /api.php [email protected] !ecash1.3.43-4! ?api? [info] [trace] StackTrace start
2023-07-20T21:31:55.536621+00:00 expensidev2004 php-fpm: tAivwu /api.php [email protected] !ecash1.3.43-4! ?api? [info] [trace] 0/1. file '/vagrant/Web-Expensify/lib/UserAPI.php' function 'createFund' line '4165'
2023-07-20T21:31:55.536624+00:00 expensidev2004 php-fpm: tAivwu /api.php [email protected] !ecash1.3.43-4! ?api? [info] [trace] 1/1. file '/vagrant/Web-Expensify/api.php' function 'addPaymentCard' line '2507'
2023-07-20T21:31:55.536626+00:00 expensidev2004 php-fpm: tAivwu /api.php [email protected] !ecash1.3.43-4! ?api? [info] [trace] StackTrace end
2023-07-20T21:31:55.536646+00:00 expensidev2004 php-fpm: tAivwu /api.php [email protected] !ecash1.3.43-4! ?api? [hmmm] An error occurred when adding payment card ExpException - 91b8a833cf82c94e68eabace586d24aa ~~ exceptionMessage: 'Auth CreateFund returned an error' exceptionFile: '/vagrant/Web-Expensify/lib/Auth.php' exceptionLine: '1541' exceptionCode: '402'

I also logged the error code and it's 402 which doesn't make sense based on the header of this file since I also tried an actual debit card and it didn't work either.

@johnmlee101
Copy link
Contributor

Do you have the most up-to-date version of auth?

@NikkiWines
Copy link
Contributor Author

Hmm, @srikarparsi this isn't dependent on any web PRs so you should be fine. FWIW when I test adding a debit card in dev I always use 4242424242424242 because that's one of stripes testing card numbers (here).

@srikarparsi
Copy link
Contributor

srikarparsi commented Jul 21, 2023

I'll try that, I do have the most up to date version of auth and also did a buildAll and restarted auth in the vm.

Copy link
Contributor

@srikarparsi srikarparsi left a comment

Choose a reason for hiding this comment

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

Added in the recordings and completed the checklist.

@srikarparsi srikarparsi merged commit c9e7f19 into main Jul 21, 2023
@srikarparsi srikarparsi deleted the nikki-remove-passwordless-dependencies branch July 21, 2023 21:04
@johnmlee101
Copy link
Contributor

Thank you so much for finishing testing! Excited that this is out!

@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.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.3.45-0 🚀

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

@@ -31,7 +31,7 @@ function Authenticate(parameters) {
// and password.
useExpensifyLogin: parameters.useExpensifyLogin,
partnerName: parameters.partnerName,
partnerPassword: parameters.partnerPassword,
partnerPassword: parameters.partnerPassyword,
Copy link
Contributor

@techievivek techievivek Jul 25, 2023

Choose a reason for hiding this comment

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

We had a typo here 😢

P.s.: Fixing this here #23532

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah oops, nice catch - thank you

@mountiny
Copy link
Contributor

Verified the contact method part works
image

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.45-7 🚀

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

Comment on lines +46 to +47
// A fresh session will not have credentials.login available.
if (!login) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changing this (and the other if in src/pages/ValidateLoginPage/index.website.js) resulted in this regression where users couldn't log in using magic links.

I should've added QA steps for testing logging in with magic links for this PR, my bad 😞

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

Successfully merging this pull request may close these issues.

6 participants