Amplify-js: aws-amplify-react: User cannot be confirm. Current status is CONFIRMED

[kennu]

Scenario: User signs up with aws-amplify-react and enters the Confirm Sign Up view, where they are expected to enter the confirmation code from an email.

While in this view, let's say the user is simultaneously confirmed by an alternative method, such as link-based confirmation (which opens in another browser window).

In this situation the user will get stuck in the sign-up flow with this error:

User cannot be confirm. Current status is CONFIRMED

If they try to resend the code, they get another error:

User is already confirmed.

My proposal is that aws-amplify-react understands that the user has already been confirmed by an alternative method and moves them forward in the sign-up flow, instead of keeping asking for confirmation which cannot happen.

[powerful23]

@kennu I will mark this as feature/enhancement request as the user could still go back to the sign in page by clicking the link in the sign up component. Thanks for your feedback!

[jordanranz]

FYI, we have started an RFC discussion for a proposed Amplify UI Component refactor to increase customizability and flexibility for our components. Please feel free to add any additional comments to the following issue:

3279

[nite]

"User cannot be confirm"

You could at the very least proof-read your copy - this is effectively a commercial product, the front line of Cognito - I'm assuming you're being paid by them.