Activation code change every user refreshes on EmailActivator::class action page

[warcooft]

The activation code/token always changes when the user refreshes the auth/a/show page controller. Can the activation code sent to the user be the same as the first code? In case the user does not receive a token then the user has the option to send a new token via a special button/link.

Sometimes I face the following scenario:
The activation code is sent by the system but the message is delayed 1-2 minutes to the destination email, so the user thinks the first attempt failed and tries again or refresh the page. then the second message containing the activation code is delayed while the first message has just been received. Then the user enters the first code after being submitted. It turns out the first code is invalid because it has been replaced with a second code which is still delayed. and so on

I hope you guys understand what I mean, I'm not good at English. Thanks

[kenjis]

Create your custom action as you like based on the EmailActivator.
See http://shield.codeigniter.com/references/authentication/auth_actions/

[warcooft]

OK, I'll try it. Thanks in advance

[grimpirate]

I had this issue with my TOTP app. Basically, the createIdentity method of the EmailActivator class deletes all prior instances of the identity. I solved this by checking for an existing identity before creating one. You can compare/contrast with the TOTPActivator class for ideas.