You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
State your question
If a user signs up, but fails to confirm the sign up, all subsequent attempts to sign in yield a UserNotConfirmedException, regardless of whether the correct password was entered or not. This appears to go against the current documentation, which suggests that I should be seeing a success response with nextStep.signInStep == AuthSignInStep.CONFIRM_SIGN_UP. The behavior implied by the docs is preferable because it allows me to distinguish between a user that has authenticated using the correct password and one that hasn't. Previous queries about this have been closed with no real explanation. Is this something that is configurable, or is the documentation incorrect?
Which AWS Services are you utilizing?
Cognito
Provide code snippets (if applicable)
Environment(please complete the following information):
SDK Version: 2.8.2
Device Information (please complete the following information):
Device: Pixel 4 XL
If you need help with understanding how to implement something in particular then we suggest that you first look into our developer guide. You can also simplify your process of creating an application, as well as the associated backend setup by using the Amplify CLI.
The text was updated successfully, but these errors were encountered:
Hello @poliver . The latest AWS SDK version is 2.67.0. I believe you are looking for Amplify-Android. If yes please close and recreate it there so that we can triage it.
@gpanshu Apologies for any confusion. I simply posted to the same repo as the issue I linked in my original post (which exhibits the same exception). A bit confusing, since both are Android repos under the Amplify Github org.
div5yesh
added
cognito
Issues with the AWS Android SDK for Cognito
bug
Something isn't working
and removed
closing soon
Issue will auto-close if there is no additional activity within 7 days.
labels
May 4, 2023
State your question
If a user signs up, but fails to confirm the sign up, all subsequent attempts to sign in yield a
UserNotConfirmedException
, regardless of whether the correct password was entered or not. This appears to go against the current documentation, which suggests that I should be seeing a success response withnextStep.signInStep == AuthSignInStep.CONFIRM_SIGN_UP
. The behavior implied by the docs is preferable because it allows me to distinguish between a user that has authenticated using the correct password and one that hasn't. Previous queries about this have been closed with no real explanation. Is this something that is configurable, or is the documentation incorrect?Which AWS Services are you utilizing?
Cognito
Provide code snippets (if applicable)
Environment(please complete the following information):
2.8.2
Device Information (please complete the following information):
If you need help with understanding how to implement something in particular then we suggest that you first look into our developer guide. You can also simplify your process of creating an application, as well as the associated backend setup by using the Amplify CLI.
The text was updated successfully, but these errors were encountered: