On which framework/platform would you like to see this feature implemented?
React
Which UI component is this feature-request for?
Authenticator
Please describe your feature-request in detail.
Summary
When a user signs up, closes the browser before confirming, then returns and confirms their account via the Sign In flow, the Authenticator redirects to the empty Create Account tab instead of completing sign-in.
Steps to Reproduce
- Open the app and go to Create Account
- Create a new account
- When the Confirmation Code screen appears, close the browser
- Reopen the app and go to Sign In
- Sign in with the newly created credentials
- Enter the Confirmation Code when prompted
- Redirected to empty Create Account tab
- Clicking Sign In tab and signing in again works correctly
Expected Behavior
At Step 7, after confirming the account via the Sign In flow, the user should be signed in automatically — not redirected to the Create Account screen.
This is the behavior observed in the Flutter Authenticator, where confirmSignUp is followed by a direct signIn() call, completing sign-in regardless of session state.
Environment
@aws-amplify/ui-react: ^6.15.1aws-amplify: ^6.16.2- React 19
Please describe a solution you'd like.
In React's withAuthenticator, when a user completes sign-up and confirms their account in the same session, autoSignIn is invoked and sign-in completes automatically. However, when the user reaches ConfirmSignUp via the Sign In flow (e.g., after closing the browser before confirming), autoSignIn is called but always fails — because the callback registered during signUp() no longer exists in the new session, and
signIn() never registers it.
Unlike Flutter, React cannot fall back to calling signIn() directly after confirmSignUp in this case, because the password has already been cleared from the form state before autoSignIn is attempted.
The ideal fix would be to match Flutter's behavior: after entering the confirmation code from the Sign In flow, sign-in should complete automatically.
At a minimum, instead of redirecting the user to the empty Create Account tab, the Authenticator should redirect to the Sign In tab and display a message indicating that the account has been confirmed and the user needs to sign in again.
We love contributors! Is this something you'd be interested in working on?
On which framework/platform would you like to see this feature implemented?
React
Which UI component is this feature-request for?
Authenticator
Please describe your feature-request in detail.
Summary
When a user signs up, closes the browser before confirming, then returns and confirms their account via the Sign In flow, the Authenticator redirects to the empty Create Account tab instead of completing sign-in.
Steps to Reproduce
Expected Behavior
At Step 7, after confirming the account via the Sign In flow, the user should be signed in automatically — not redirected to the Create Account screen.
This is the behavior observed in the Flutter Authenticator, where
confirmSignUpis followed by a directsignIn()call, completing sign-in regardless of session state.Environment
@aws-amplify/ui-react: ^6.15.1aws-amplify: ^6.16.2Please describe a solution you'd like.
In React's withAuthenticator, when a user completes sign-up and confirms their account in the same session, autoSignIn is invoked and sign-in completes automatically. However, when the user reaches ConfirmSignUp via the Sign In flow (e.g., after closing the browser before confirming), autoSignIn is called but always fails — because the callback registered during signUp() no longer exists in the new session, and
signIn() never registers it.
Unlike Flutter, React cannot fall back to calling signIn() directly after confirmSignUp in this case, because the password has already been cleared from the form state before autoSignIn is attempted.
The ideal fix would be to match Flutter's behavior: after entering the confirmation code from the Sign In flow, sign-in should complete automatically.
At a minimum, instead of redirecting the user to the empty Create Account tab, the Authenticator should redirect to the Sign In tab and display a message indicating that the account has been confirmed and the user needs to sign in again.
We love contributors! Is this something you'd be interested in working on?