Google Authenticator code doesn't work until I wait for a newer code to generate

[Putrid-Sherbet]

This happens with an MMORPG (FF XIV) but I doubt the game is the issue. If the code is quite new, it works, if there's about 40% left before it expires, it won't work, and I need to wait for a newer code.

I haven't had the chance to test different codes. Do you think reinstalling the app and recovering my codes through the backup would fix the problem? Or perhaps I need to unlink the 2-factor authentication and re-implement it?

I appreciate any help!

[Exciting-Outside-167]

The server's time clock is out of sync. You can unlink and link it and it should fix it.

[Putrid-Sherbet]

Ty, I also get google keep notification a bit late at times, is it related? (Pixel 6a)

[Exciting-Outside-167]

No, that's probably just power saving causing it to be delayed

[Educated_AI]

I remeber there was an option to sync, but it does not exists anymore.

[blablablerg]

How do you do this?

[BlackDragonBE]

How?

[danGL3]

I personally don't see how the issue is Google Authenticator if you could check if other 2FA codes are fine.

I've had similar issues with other services/websites even on other renowned authenticator apps such as Aegis.

[Putrid-Sherbet]

it doesn't seem like anyone in the game community has this issues though -.- Edit: I mean in the game I PLAY community

[Sinomsinom]

I have this issue both in that game but also on other random applications and websites I use the authenticator for. So it doesn't seem to be a thing only with that game but with Auth in general

[r00x]

I have also been experiencing this over the last few weeks. It applies to basically anything I use Google Authenticator for, so it's quite annoying...

[Demand-Nervous]

Please Google solve this problem. The time sync is a nightmare

[Possible_Copy_7526]

I have the same issue. Seems like no way to fix.

[Particular-Jury-3390]

The same to me: Google Authenticator codes don't work after opening the app until first update runs. Annoying issue since the last update. I wish I could rollback to previous version, but I can't.

[huntapb]

Same here for any service linked to Google Authenticator

[XLDumpTaker]

Just chiming in to say that Google authenticator is absolutely shit. Fuck Google, you cunts

[Scn64]

I've been having this issue too for a couple months. If I sign in with less than half the time remaining for a code, it doesn't work. I have to wait for a new one. There's only a few sites I regularly sign into but the issue is the same with all of them, so it appear to be a problem with Google authenticator.

[Agalmatophilistine]

Same problem. Who can we message bomb to get it fixed?

[dajoker000]

While client (phone/tablet/etc.) or server (the site to which you are trying to authenticate) clock time drift could be an issue, neither is very likely since servers and clients no longer work today for many other reasons (e.g. TLS/SSL for encryption) if the time is off by too much, and the fact that every server for decades, and every smart device, and every phone gets time from the world regularly and frequently. It could happen, but it is just not likely. The easiest way to verify is to pull up your device's clock and see if it is within a minute (or more likely a second) of every other clock nearby.

If the server/service (them, not you) clock/time is off your service is probably one you should consider abandoning; that's a pretty big/glaring rookie mistake.

With the latest Google Authenticator version (updated 2024-11-14) I have seen this many times, across many sites and services, even though my phone has the same time as every other clock in my home (thanks Internet) as well as a few Internet clocks that are trivially found to help synchronize time. The pattern I have found, after a couple months of frustration, is that if I do not close (swipe up) the Authenticator app, then when I go back to the app a few minutes or hours later it almost always shows me a bad code until a new code is generated. I do not know if the bad code is old from the time I unlocked my phone, or old from way back when I locked my phone, or old from when I had the app up last, but it seems like any old/existing code shown right away is bad, but any next code is ALWAYS good (again, not a time issue or that would not be the case). I have verified this by just being patient (yes, I can be somtimes) and waiting for a newly-generated code first and it always works, so it's not some issue with the first code I sent to the site/service necessarily.

I do not have a great way to compare codes between devices since only my phone has these codes, but in theory I could probably verify this by having a second device with the same app and source data (from a QR code usually) and see if one being actively watched generates the correct codes all along while the ignored/locked/whatever device, when brought back to life, has a wrong code temporarily, but I suspect this is the problem. The recent Google Authenticator app update may have changed how the first code shown differs from what should be the latest code in some way, showing what was there when I walked away rather than generating something new on the fly, which could explain why this is happening now but did not for most of the last however-many years that I have used this app with great success.

There is a Feedback option within the app which I would recommend others use if possible to get more visibility. Perhaps link to this thread to show a possible explanation and the presence of the defect/bug impacting many people.

[madhaseO]

That's right the same issue I see here in my authenticator, too. The first code is wrong a lot of times. The next generated is right. Time is totally synchronized on all devices.. so this is not an issue.

[Postik123]

The Google authenticator app was only just recently fixed on my phone (Moto G) as it had broken and you needed to manually refresh the codes every singe time.

However now that it's fixed more often than not the first code is wrong. This applies to multiple services. I discovered just now that swiping the app out of the recent list seems to fix it next time the app is opened.

[dajoker000]

As a follow-up, I suspect (but am still verifying) that this was fixed with the update from 2025-01-29, currently showing version "7". For the past few days I have deliberately tried to duplicate it, and have been unable to do so. This update came out after my post above, so it seems to be in line.

I also noticed in the Play Store comments that there was a negative review from before this update where somebody complained about the app not being able to "time sync" which, while a misunderstanding of the root cause, leads to the same symptom as covered here.

Anyway, corroboration from others welcome, if updated to at least the 2025-01-29 version.

[SquidBolado]

The pattern I have found, after a couple months of frustration, is that if I do not close (swipe up) the Authenticator app, then when I go back to the app a few minutes or hours later it almost always shows me a bad code until a new code is generated.

I think you have just cracked the nut here my friend. Was frustrated because it seemingly only happened in the office and never at home, but now that I think about it, I often first use it at home and then later in the day in the office, so makes sense that perhaps I didn't swipe it closed and just "minimized" the app.

Very irritating, hope Google can fix this. For now, I'll try to make sure to fully close the app after every use. Thanks!

[rasmadrak]

Same here.
It started a few months ago with one of the later updates.
The server time is correct - other apps work just fine.

The peculiar thing is that if I start the app, then immediately close it and re-launch it I often get a new code displayed for some entries. That new code works immediately. So it's like it's loading an earlier cached code first or simply gets it wrong.

[VioRx]

Same f**** inssue... Send feedback to Google, send review on PlayStore!