Identify where the code comes from
SMS, email and authenticator codes arrive differently. This guide focuses on an already configured authenticator. Google states that Authenticator can generate codes without internet or mobile service, but the website still needs connectivity to submit a login. Offline generation is not offline sign-in.
Check the entry and clock, then retry once
- Verify the real website domain and distinguish a rejected or expired code from a network submission error.
- Match the authenticator’s service name and account identifier to the account being accessed.
- Use a fresh code within its validity period rather than repeatedly trying an expired code or an old screenshot.
- Check automatic date, time and time zone on the phone. Do not rely on old instructions for a removed in-app Authenticator time-correction option.
- If it still fails, use a previously configured backup method or the site’s official recovery process. Do not delete the entry or send setup QR codes to support.
Keep codes and setup secrets out of reports
Share the domain, error, time and page-loading status while redacting codes, backup codes, setup secrets and QR codes. Google backup methods depend on what the account already has configured. They do not establish identical Yunbao or other-site features or guarantee recovery.