Users Who Did Not Verify on Registration Should Be Redirected to ConfirmSignUp Page

[rajleechaudry]

On which framework/platform would you like to see this feature implemented?

React Native

Which UI component is this feature-request for?

Authenticator

Please describe your feature-request in detail.

If a user registers through Amplify Cognito, but doesn't immediately verify their confirmation code, then tries to come back later and login, they should be auto redirected to the ConfirmSignUp. Amplify itself returns the response on signIn of {"isSignedIn": false, "nextStep": {"signInStep": "CONFIRM_SIGN_UP"}}

But the flow does not get redirected. This is pretty odd, and works in the SignUp flow. I.E. When a user signs up, they get redirected to the ConfirmSignUp.

Please describe a solution you'd like.

Unverified User Tries to signIN -> some way to redirect them to ConfirmSignUp component w/o doing a hack like leaving the Amplify auth navigator to put up my own confirmation page, and then redirect back to the Authenticator. There should be a setting or it should be automatic that Amplify follows it's own returned next step "CONFIRM_SIGN_UP"

We love contributors! Is this something you'd be interested in working on?

• 👋 I may be able to implement this feature request.
• ⚠️ This feature might incur a breaking change.

[cwomack]

Hello, @rajleechaudry 👋. It sounds like you're asking for the immediate rendering of the "confirm sign in" screen to happen upon app launch in situations where a user wasn't able to complete the sign up flow, but then comes back later to the app. Is that correct?

With this being opened as a feature request and that being a departure from the currently functionality, just want to confirm the ask here. Thanks!

[rajleechaudry]

Hello,Not on app startup (for example our app has a non-Auth experience as well) but on any attempted login after after signing up, until email/phone confirmation is complete. If you didn’t verify your email for instance then the next logical step for you is always going to be to verify, no matter how long after you come back. Agreed?Another approach, and probably better, would be to implement a toConfirmSignUp instruction similar to toSignIn, and leave it up the developer.E.g. const {toConfirmSignUp} = useAurhenticator()At the moment there isn’t a way I can find to handle this without doing something unnatural (bouncing outside of Cognito, using the Navigator directly, etc). I.E. If I signed up, but didn’t verify, then try to signIn, Amplify/Cog sends the user a code, but I have no amplify way to redirect to the ConfirmSignUp. I could message the user saying “You’re not verified enter your code” in an alert, but where would they do that, because now you’re back to another problem the out-of box confirm sign up page isn’t linked on the other pages, and there isn’t a toConfirmSignUp instruction in useAuthenticator hook. So basically the user is stuck and has to re-register.My solution at the moment is to call the confirmSignUp method directly and override the ConfirmSignUp component for both signIn and signUp, for the signIn -> confirmSignUp flow I redirect using my main nav, again unnatural and also time wasted implementing a low value page myself that’s available be out of box.👍 Thanks for picking upOn Jan 15, 2025, at 12:54 AM, Chris Womack ***@***.***> wrote: Hello, @rajleechaudry 👋. It sounds like you're asking for the immediate rendering of the "confirm sign in" screen to happen upon app launch in situations where a user wasn't able to complete the sign up flow, but then comes back later to the app. Is that correct? With this being opened as a feature request and that being a departure from the currently functionality, just want to confirm the ask here. Thanks! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[cwomack]

@rajleechaudry, thanks for the reply and additional context. I want to make sure we're not potentially talking about an existing feature request (and poor user experience) that is well known and referenced in this issue on the amplify-js repo where users can get into a "deadlocked" state when they haven't confirmed their account with Cognito, but have attempted to sign up.

Does that issue capture the situations you're describing? If not, then can you help us understand the difference in the ask here? If we can consolidate this feature request into that issue and get another "+1" of another customer experiencing this blocker that requires Cognito implementation to change, then it helps us gain traction. Thanks!

[ysabri]

I'm commenting to clarify one thing because I do believe it could be a similar request.

My issue was filed in V5 which could cause confusion given that a lot of the API and hub events changed since.

I do ask for what they ask for here: aws-amplify/amplify-js#11270 (comment)

One thing @rajleechaudry hasn't clarified, is whether they set the autoSignIn flag to true when calling the signUp method. We do this and end up with accounts that are Confirmed and have the email User Attribute as Not verified. In that case, there is no way for us to trigger the email verification flow in the Authenticator.

If we were not to set the autoSignIn flag when calling signUp, back in v5, the Authenticator will go into the confirm signup flow which on success will set the user as Confirmed and email User Attribute as Verified.

Meaning, in the Authenticator, for unauthenticated users, there is no way to trigger the email User Attribute verification flow if their account is marked as Confirmed.

[jordanvn]

Hi @ysabri, thanks for providing additional information.

We do this and end up with accounts that are Confirmed and have the email User Attribute as Not verified.

This sounds like a potential bug, so I have opened #6316 to bring it to attention for triaging.