fix(auth): Fix losing session identifier when incorrect otp code is entered during confirm sign up #3136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: #3135
Description of changes:
Fixes one of the issues identified in the linked bug. When a user entered an incorrect confirmation code during
confirmSignUpwe would enter an Error state. During a correct subsequentconfirmSignUpcall we would not pass the existing Cognitosessionidentifier. If there are no passwordless options enabled for the user pool, this would result in Cognito throwing aSelectChallengewhich would cause Amplify to hang.This fix retains the
signUpDataduring the error state so that thesessioncan be continued on subsequent calls toconfirmSignUp. This allows Cognito to recognize the password entered during initial sign up, allowingautoSignInto succeed.Fixing
autoSignInhanging onSelectChallengeis a much larger fix that will be tackled separately.How did you test these changes?
Documentation update required?
General Checklist
fix(storage): message,feat(auth): message,chore(all): message)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.