@W-17458039 - Handle error states for social/passwordless login and reset password

[yunakim714]

Description

Before releasing social and passwordless login, we need to ensure that all error states are covered and presented in the UI.
The following spreadsheet details different error scenarios for social and passwordless login, and what error message is prompted after the error: Social/Passwordless Login Error States

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• Add error handling for the different possible scenarios detailed in the above spreadsheet

How to Test-Drive This PR

• Manually step through each scenario in the spreadsheet and verify that you can see the correct error message

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[hajinsuha1]

@yunakim714 It seems like users aren't able to resubmit for passwordless login after they cause an error.

Steps to reproduce:

1. Open the auth modal/login page
2. Enter a non existent user's email like a@a
3. Click Continue Securely
4. Enter an existent user's email like [email protected]

Expected:

• /passwordless/login API call is made and check email page is displayed

Actual:

• /passwordless/login API call is not made and login page is still displayed

[yunakim714]

@hajinsuha1 Resolved the bug! Let me know if you still see the issue. Thanks for pointing that out!