2FA login is not working after switching device with "change device" option.
I've recently changed my device and the option to "change device" for 2FA is not really working. Three times I burned two of my login attempts on wrong codes, that's a total of 6 wrong codes. Every time I had to login with the code provided via email.
The point is that to make it *take*, I had to remove 2FA altogether and then add my new device.
So once again, the "change device" does nothing at all. You are seemingly left with 2FA on, because the code generated by the new authenticator is accepted in torn settings. However it is not registered/paired correctly and I am not able to log in with it right after. I cannot say if the old authenticator would still work in this case as that has been removed already before the switch.
This happened around 08/25. On the day or before it.
What's going on an whose fault is it?
CloudJumper[1636201]Staff · #2
I am unsure who the correct developer for this would be. Passing along to Joe for re-assignment.
You're right that we don't have a confirmation process once a 2FA device has been added, we just assume all's fine. If a mistake was made, can't you login with the email code and change it again?
I can, but presumably a feature that is broken or does not work all the time or in a predictable manner, most likely should not be present at all?
Leaving it as is, crossing your fingers and hoping for the best does not seem like a good practice.
If the correct or 100% foolproof way to change your 2FA is to remove it completely and add it from scratch, I would suggest removing the option to "change" it altogether.
I am no genius, but someone less savvy, who is unable to login, might not return to the game at all, especially if they locked themselves out of their account and the procedure to get back in (emails, verification or whatnot; I do not know what are the steps after 3 failed 2FA codes have been used) is too annoying or long.
That is a risk, as tiny as it may be.
Current state is imo not acceptable and confusing/misleading.
I've just tested the system and it all appears to be working fine, I wonder if you missed the "NEXT" button below the QR code? Please try again, or maybe I'm misunderstanding something.
Just changed the authenticator twice successfully. So at the moment I cannot reproduce it either. However there should clearly be six failed attempts in the logs around 08/25. I am not doing anything differently now, if you cant see anything wrong on your end - close this.
If you notice it again, please create a new report. I know there's just under 8,000 people using the authenticator 2FA currently, and this is the first I've heard of this problem. Let's see if anyone else mentions it in the future.
I have noticed this issue. Android 10 , switched from Google Authenticator to Authy. I have paired through the settings with Authy and when I try to login in a new browser using the code from Authy, I get an incorrect message.
I have reseted to Authy twice and still same issue.
Hello It seems the issue is related to unsynchronized time in the authentification app. Please follow the instructions in the error message (https://i.imgur.com/kSNlF8n.png). After that, the issue should go. Thanks!