If Google Authenticator codes are rejected, first check the service and account, then the phone’s time. Do not delete the entry or reinstall the app before confirming that you have another way to sign in.
Check the entry and challenge
Authenticator can hold codes for many websites and several Google Accounts. Select the entry for the exact service and username you are trying to access.
Confirm that the page is asking for an authenticator-app code rather than an SMS code or a backup code. Copying the correct-looking number from the wrong entry will not satisfy the challenge.
Use a fresh code
Enter the code while it is still current. If it is about to expire, use the next code rather than repeatedly submitting the one that just ended. Keep the attempt within the legitimate sign-in flow you initiated.
If the service reports an attempt restriction, follow that instruction instead of submitting each newly generated code indefinitely.
Check the operating system’s clock
Google’s current guide says Authenticator version 7.0 no longer has the old in-app time-correction setting. The app uses the operating system’s time.
- Open the phone’s date-and-time settings.
- Check that the date, time, and local time-zone settings are correct.
- Use the operating system’s automatic time synchronization where appropriate.
- Return to Authenticator and test a fresh code.
Do not follow an old tutorial that insists on a missing Time correction for codes menu. Do not manually move the clock forward or backward until a code happens to work.
Consider enrollment and activation
If the authenticator was newly configured, check whether setup completed and whether Google has made the method available for sign-in. Its guide notes a possible trust delay for a new Authenticator method.
If a site’s authenticator enrollment was replaced, an older entry may still generate numbers that the site no longer accepts. Use a working backup to inspect the site’s current setup before removing anything.
Preserve the remaining access
Reinstalling or deleting entries can destroy useful local access, and deleting a synchronized entry affects other synced devices. Use a supported backup method or official account recovery if necessary. For codes belonging to another provider, follow that provider’s recovery process; Google Authenticator itself cannot override its verification decision.
Official references
Reviewed against Google’s official guidance on October 27, 2026. Available options and screen labels can vary by account, device, region, and organization policy.