Users can enter state where account is `Confirmed` but email User Attribute is `Not Verified`

[jordanvn]

Potential bug based on issue referenced in #6295

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.

Originally posted by @ysabri in #6295