Google Authenticator updated with internal clock sync

If you're using two-step authentication for your Google account, you'll want to pick up the latest version of the Authenticator app, which brings a new time syncing feature to ensure correct codes are generated. Previously, if the app's internal clock went too out of sync with Google's, the Authenticator would generate incorrect codes. The new syncing feature remedies this by allowing users to sync the clocks through a new settings page.

With an app as crucial as the Google Authenticator, you'll want to make sure you're always up to date. This one's a manual update, so head to the "My apps" menu in the Google Play Store to grab the new version.

Alex Dobie
Executive Editor

Alex was with Android Central for over a decade, producing written and video content for the site, and served as global Executive Editor from 2016 to 2022.

  • Huh. I've never had this problem and I've been using 2-step since it came out. *shrugs* Higher reliability is always welcome.
  • There is some concern over the proper handling of leap seconds on certain cell networks or devices that only use GPS as a source of time. It seems to be pretty rare in the real world but apparently someone was complaining enough.
  • Its not that rare. And the clock drift being discussed here has nothing to do with leap seconds. They are talking about much larger time drifts than a few seconds. If you have an android device that expects to get clock updates from cell towers, simply being in airplane mode for a will allow significant clock drift. My Nexus One, no longer having a Sim since I moved to a HOX, has a clock drift of about 14 minutes, because it has no cellular time source. The same is true for some tablets. Android has been inconsistent in its use of NTP servers on devices designed for cellular connection. They often drift when connected to wifi only.