Cyber SecurityIntermediate

Google Verification Code Not Working or Not Arriving? Troubleshooting Guide

Quick Answer If a Google verification code fails, first match the account, verification method, and current sign-in request. A 10-digit Android security code...

Bison Technical Team Enterprise IT specialists

Updated 05 May 2026 7 min read 48,721 total views

Structured technical guidanceSafety notes included where requiredSources listed below

Quick Answer

If a Google verification code fails, first match the account, verification method, and current sign-in request. A 10-digit Android security code cannot replace an 8-digit backup code. For Authenticator errors, check the selected entry, expiry, and device time. For missing SMS or prompts, confirm which delivery method Google actually selected before requesting another message.

This guide diagnoses verification failures. If you need instructions for obtaining your first code or recovering an account without usable verification methods, see g.co/sc: obtaining Google security codes and recovering access.

Identify What Google Is Asking You to Use

The words on the verification screen determine the next step. A request to verify your identity is not, by itself, proof that your account has been compromised.

Requested method	What belongs here	Common mismatch
Android security code	The 10-digit code from the relevant account's Android settings	Entering a code from Authenticator instead
Authenticator code	A current code from the entry configured for that account and service	Using an expired code or the entry for another service
Backup code	An unused 8-digit code from the account's current backup set	Using a previously consumed code or a replaced set
Text-message verification	The code sent to the phone number shown by Google	Using an older message after requesting a replacement
Google prompt	Approval on an eligible signed-in device, with number matching if requested	Waiting for an SMS when Google sent an app prompt
Passkey or physical security key	The requested device-based verification	Looking for a numeric code when the screen requires a different method

Practical first check: Compare the full email address on the requesting screen with the account on your phone or in the app. If you have several accounts, do not rely on the profile picture alone. As a troubleshooting precaution, keep one active verification attempt in view so that you can track which request you are completing.

A Code Arrives or Is Generated, but Google Rejects It

Android security code is rejected

Confirm the requesting screen specifically asks for an Android security code.
Check that the Android device is supplying a code for the same Google Account.
Compare all ten digits before submitting. Do not remove digits to fit another method's field.
If the matching code still fails, use Try another way when available rather than repeatedly submitting the same value.

The phone does not need internet or mobile service to generate an Android security code. Therefore, loss of mobile coverage alone does not explain why a correctly obtained code is rejected. The device submitting it online still needs a working connection.

Google Authenticator reports an incorrect code

Select the entry for the exact service and account you are signing into.
Submit the code before it expires. If its timer is nearly finished, wait for the next code.
Check that the phone's date, time, and time zone are correct. Use the operating system's automatic time settings where available, then try a new code.

Current app behavior: Google states that the in-app time-correction setting was removed in version 7.0. Authenticator uses the operating system's time, so older instructions directing you to an in-app time-sync command no longer apply to that version.

Warning: Do not delete an Authenticator entry as a routine troubleshooting step. Deleting a synced entry also removes it from other synced devices. Establish another working sign-in method before changing its configuration.

If entries are missing, check the profile selected inside Authenticator. If you cannot restore access to the required entry, use an available backup method or account recovery.

A saved backup code does not work

Check three conditions: the backup-code method is selected, the code has never been used, and it belongs to the current set for this account. Generating a replacement set invalidates all codes in the previous set, including unused ones.

A backup code does not periodically refresh like an Authenticator code. Waiting for a new time interval will not repair a used or revoked code. Try another unused code from the current set, if available. Do not discard your last accessible copy while investigating.

The Verification Message or Prompt Never Arrives

Google says it sent a text message

Check the displayed phone-number ending against the number you currently control.
Check mobile reception and whether the phone and service plan can receive SMS.
If Google offers a resend option, request a replacement and use the newest code.
If delivery continues to fail, check messaging availability with your carrier or select another offered verification method.

If SMS is not offered at all, treat that as a different problem from failed delivery. Google may select another challenge, particularly when the sign-in differs from normal activity. Repeatedly checking your SMS inbox will not help when no text was sent.

Google asks you to check your phone, but no prompt appears

Connect the receiving phone to Wi-Fi or mobile data; prompts need internet access.
Confirm that the relevant Google Account is signed in on the receiving device.
On iPhone or iPad, open an already signed-in supported app, such as Gmail, Google, YouTube, or Google Photos. Check its notification permissions.
Return to the requesting screen and use Resend if available.

If the phone displays Request Expired for a sign-in you initiated, resend from the active sign-in screen and complete the new request. If you did not initiate a sign-in request, decline it and review your account's sign-in activity.

If the receiving phone is inaccessible or signed out, switch to another offered method. Installing a Google app alone does not establish the signed-in account needed to receive its prompt.

g.co/sc Keeps Returning to the Sign-In Screen

Google documents g.co/sc as a security-code option when a security key cannot be used. Its procedure starts on a device already signed into the affected account.

Use these practical checks to distinguish a session problem from an unavailable verification method:

Wrong account: Check which account is active in that browser profile.
Different browser context: A private window or another browser profile may not contain the session you expected.
App access only: A signed-in Gmail app does not establish that the browser has a working Google session.
Same inaccessible challenge: If the page requires verification you cannot complete, return to the original flow and select another available method.

Preserve a working session on a device you still control. Clearing its browser data or signing out may remove useful access. A new window does not bypass verification, and this address cannot generate an unrestricted recovery code for a signed-out account.

You Can Open Gmail, but a Sensitive Action Is Blocked

If you can read your email but cannot change a password or complete another sensitive action, diagnose that action separately from account sign-in.

Google may temporarily restrict sensitive changes when it cannot verify identity. Its guidance describes seven-day restrictions and trust requirements for newly associated devices or verification methods. Existing account access can continue during that restriction.

Follow the instructions for the specific blocked action. Where offered, use an established verification method or a familiar device. Do not assume that an SMS or Android code must be accepted for every security-sensitive change. Google also states that verifying a new sign-in method can require a trusted passkey or physical security key.

Different from account recovery: A recovery security hold can last hours or days according to risk factors. The seven-day sensitive-action guidance is not a universal waiting period for every login error. Follow the timing displayed in your own flow.

Decide Whether to Continue Troubleshooting or Start Recovery

Result of your checks	Next step
The account or verification method was wrong	Correct that mismatch and complete the requested method.
The code or prompt was accepted	Continue through any remaining verification and confirm the intended account opens.
You can sign in, but a specific change remains blocked	Follow the sensitive-action instructions and any displayed wait.
No offered verification method is accessible	Start Google Account Recovery.
A recovery security hold is already active	Follow Google's instructions. If another verification method becomes available, a new attempt using it may help.
This is a work or school account	Contact your organization's administrator when backup options fail.

For the full recovery procedure and preparation of backup methods, use BISONKB's Google security-code and account-recovery guide.

What to Record When Asking IT Support for Help

A useful diagnostic summary includes the exact error wording, the requested verification method, whether anything arrived, the device and browser or app involved, and whether you can still open the account elsewhere. Note whether the failure affects sign-in or only a specific account change.

Keep passwords, actual verification codes, backup-code lists, and Authenticator setup or transfer QR codes out of support tickets. If sharing a screenshot, redact those details and unnecessary personal information first.

Sources

Official documentation checked on 26 October 2026.

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.