[Authenticator] Cannot confirm sign up when using phone + email config and signing up with phone

[Jordan-Nelson]

Description

When phone OR email is chosen to be used as the username, and the user signs up with phone number, they are unable to confirm their sign up. The Confirm Sign Up screen shows "email" as the username even though phone number was used during sign up. As a result, the email validator is used. See the screenshot below where the username is a phone number, but the label says "email".

When this issues is addressed, we should also test the scenario where a user signed up but did not confirm their account, and then later attempts to sign in (which will redirect them to confirm sign up).

Categories

• Analytics
• API (REST)
• API (GraphQL)
• Auth
• Authenticator
• DataStore
• Storage

Steps to Reproduce

No response

Screenshots

No response

Platforms

• iOS
• Android

Android Device/Emulator API Level

No response

Environment

N/A

Dependencies

vNext

Device

N/A

OS

N/A

CLI Version

N/A

Additional Context

No response

[Jordan-Nelson]

Note: I am seeing this on /next. I have not confirmed this is present in the latest release.

[Jordan-Nelson]

The linked PR seems to address it. Need to do more testing and confirm if this also needs to be fixed in main.

[Jordan-Nelson]

The issue does exist in main as well.

[Jordan-Nelson]

Addressed by #1785

[Jordan-Nelson]

fixed in the latest version of amplify_authenticator (0.2.1)