Resend Code on SignUp doesn't resend the code (using Cognito emailing)

[guy-ecton]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have tried disabling all browser extensions or using a different browser
• I have tried deleting the node_modules folder and reinstalling my dependencies
• I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

React

Which UI component?

Authenticator

How is your app built?

Vite, Amplify UI (no Amplify BE)

What browsers are you seeing the problem on?

No response

Which region are you seeing the problem in?

us-east-1

Please describe your bug.

• using
• using alias_attributes = ["email"]
• using Amplify UI only (no Amplify BE)

Signup works, user gets 6 digit code to the email.

User clicks "Resend Code".
User doesn't get another email with new code.

What's the expected behaviour?

User should get another email with a new 6 digit code.
I checked, emails don't go to spam.
New signup (to the same email after I delete it from Cognito) does get the first email.

The HTTP that gets sent upon clicking Resend Code:

POST https://cognito-idp.us-east-1.amazonaws.com/
x-amz-target: AWSCognitoIdentityProviderService.ResendConfirmationCode
payload: {
  ClientId:"f7gir36xxxxxxxxxxxx",
  Username: "hedxxxxx@bexxxxxx.com"
}

and it returns with 200OK with:

{"CodeDeliveryDetails":{"AttributeName":"email","DeliveryMedium":"EMAIL","Destination":"h***@b***"}}

Help us reproduce the bug!

1. Cognito User Pool
2. alias_attributes = ["email"]
3. email verification code send by Cognito (haven't tried with SES yet)
4. Use Amplify UI

<Authenticator components={{handleSignUp}}>...</Authenticator>

5. Signup with email+password (username is generated as a random UUID4 string)

const handleSignUp: typeof signUp = async (data) => {
  const uuid = crypto.randomUUID()
  data.username = uuid
  return await signUp(data)
}

6. see 1st email with code
7. click Resend Code
8. 2nd email doesn't arrive

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

No response

[osama-rizk]

Hi @guy-ecton ,

Thank you for creating this issue. We will investigate and get back to you once we have more information.

[osama-rizk]

Hi @guy-ecton ,

<Authenticator components={{handleSignUp}}>...</Authenticator>

The above syntax is not correct did you mean services prop i.e <Authenticator services={{ handleSignUp }}> ?

Also, Could you please provide the following information such as:

• package.json
• Your config file . Or that log console.log("Amplify.getConfig()", Amplify.getConfig());. Please redact all of the resources information (e.g identity_pool_id)
• Any error messages or logs
• Minimal reproduction example or sample app

This information will help us better understand and address the issue.

Thanks!

[guy-ecton]

Hi
Yes, obviously I made a mistake and this should be

<Authenticator services={{handleSignUp}}>...</Authenticator>

I should let you know that ticket was escalated to AWS Support and they could reproduce this issue on their side.
So while not directly an issue for Amplify UI I think it should be raised, and maybe we can come up with a workaround.

package.json

{
  "name": "test",
  "version": "0.0.1",
  "type": "module",
  "scripts": {
    "dev": "vite",
  },
  "dependencies": {
    "@aws-amplify/ui-react": "^6.12.0",
    "aws-amplify": "^6.15.5",
    "react": "^19.1.1",
    "react-dom": "^19.1.1",
  },
  "devDependencies": {
    "typescript": "^5.9.2",
    "vite": "^7.1.3",
    "vite-tsconfig-paths": "^5.1.4",
    "vitest": "^3.2.4"
  }
}

Amplify configuration

{
  Auth: {
    Cognito: {
      userPoolId: "...",
      userPoolClientId: "...",
      loginWith: {
        email: true,
      },
      userAttributes: { email: { required: true } },
    },
  },
}

Errors and logs
No error is thrown, the opposite is true- the request returns in 200OK and is attached in the first message.

Reproduction
Is easy - try to sign up, get the mail, click ResendCode (or trigger the equivalent API call to Cognito, it doesn't matter) and see that the code doesn't arrive. I can't attach a reproduce right now.

The only way we got it working is by temporary marking the user to have "verified email" in Cognito console - then the ResendCode worked. Obviously should not happen, made just for debugging.

[bobbor]

hey @guy-ecton

sorry for not replying in a timely manner.
I'll be taking a look at this problem in the following days and hope we can solve this issue.

[bobbor]

Hey @guy-ecton

I had a look at the issue and unfortunately I am not able to reproduce the issue as described.

When using the <Authenticator /> as documented without a service definition, I can:

1. signUp
2. receive a confirmation code
3. re-send and receive a new confirmation code
4. repeat 3 however often I want - all previous codes expire and become invalid.

NOTE:: sending and receiving a new code from the signUp-form will take 1 - 2 minutes (like real 2 minutes).

---

however, when using (as described in the original post)

<Authenticator services={{
  handleSignUp: async (data) => {
    const uuid = crypto.randomUUID();
    data.username = uuid;
    return await signUp(data);
  }
}}/>

this will fail, as the username NEEDS to be an email.

{
  "__type": "InvalidParameterException",
  "message": "Username should be an email."
}

see your configuration:

{
  Auth: {
    Cognito: {
      userPoolId: "...",
      userPoolClientId: "...",
      loginWith: {
        email: true,
      },
      userAttributes: { email: { required: true } },
    },
  },
}

---

can you check from which email your cognito uses as "from" for the confirmation codes?
It might sound silly, but maybe that email is blocked/marked as spam, when receiving similar looking emails to often. (some email client might do this)

[bobbor]

At this point some small sample App would be beneficial.

It does not need to be a full application, just something which is known to cause and reproduce the issue.