Reinstalling Google Authenticator does not automatically restore entries that existed only on the old installation. Check the synchronization account and remaining devices before making further changes.
Check which Google Account is selected
Open Authenticator’s profile menu and inspect the complete account address. If the entries were synchronized, sign in with the identity that actually stored them.
Authenticator can work with several Google Accounts. An empty list under one identity does not prove that entries stored under another identity were erased.
Determine whether the codes were local only
If you used Authenticator without a Google Account, the codes may have been stored only on the device. Reinstalling the app is not a promise that those local secrets will return.
If another device still has the entries, preserve it and investigate the supported synchronization or manual-transfer route. Do not delete entries on that device while diagnosing the missing copy.
Avoid a destructive mode change
Google’s guide mentions both account selection and use without an account when discussing missing codes. Its separate warning says that switching to Use Authenticator without an account removes previously synchronized codes from Google Accounts and leaves them on the device.
For that reason, identify the existing storage mode before changing it. Do not treat the switch as a harmless refresh button.
Check whether deletion synchronized
Deleting a synchronized entry removes it from other synced devices too. If that happened, reinstalling again is not a documented recovery method. Avoid creating replacement entries with guessed setup information.
A time-setting problem causes rejected codes, not normally an empty account list. Changing the clock will not reconstruct missing authenticator secrets.
Use the provider’s backup or recovery
For Google, try an established backup code, prompt, security key, passkey, or other method offered at sign-in. If none remains, use official account recovery.
For another website’s entry, use that provider’s backup codes or recovery process. After regaining access, enroll Authenticator again through the site’s security settings and test a new code. Keep an independent backup before removing the old enrollment. Google Authenticator cannot authorize a replacement on behalf of an unrelated provider.
Official references
- Get verification codes with Google Authenticator
- Fix common issues with 2-Step Verification
- How to recover your Google Account or Gmail
Reviewed against Google’s official guidance on October 27, 2026. Available options and screen labels can vary by account, device, region, and organization policy.