-
Notifications
You must be signed in to change notification settings - Fork 312
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
Amplify error: User is not confirmed #4542
Comments
Hi @christianswanepoel thank you for opening this issue. It looks like you are using the Authenticator UI component with this issue. I'm transferring this over to the UI repo for better assistance. |
Hey @christianswanepoel, thanks for bringing this to our attention and sorry for the delay. We have been able to reproduce this issue and will be working on a fix. |
Hi @christianswanepoel, |
Hi @reesscot
|
@christianswanepoel The |
Before opening, please confirm:
JavaScript Framework
Next.js
Amplify APIs
Authentication
Amplify Categories
auth
Environment information
Describe the bug
Should the user refresh or close the browser window before entering their emailed confirmation code, and return to app and logging in:
cognito will return a 400 code with body...
Amplify Authenticator displays on screen an incorrect message stating a TEXT message was sent.
Expected behavior
When registering a new user and entering the emailed code everything works as expected and Cognito returns 200 with body...
Amplify Authenticator displays the correct message stating an EMAIL message was sent.
Reproduction steps
Create a user and refresh the browser window, then login using the same details as when registering.
Code Snippet
// Put your code below this line.
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
To make the issue worse is that both the above examples will return via
ConfirmSignUp
.The text was updated successfully, but these errors were encountered: