SEO Title

Google prompt not showing on Android? How to fix it

Google prompt not showing on Android? What to test before using a backup code

If a Google prompt does not appear on your Android phone during sign-in, that does not automatically mean your account is broken or compromised. Google's official guidance says to test internet access, `Do Not Disturb`, updated `Google Play services`, and whether the phone is still signed in to the same Google Account before you fall back to another second step [F1][F2]. Only after that does it make sense to use a backup code, a backup phone number, a passkey on another device, or another recovery path [F2][F3].

That order matters because Google explicitly recommends prompts over SMS for stronger protection against SIM swap and other phone-number attacks [F2]. Before you burn a backup code, it is worth checking whether the problem is only local to the device.

Quick answer

  1. On the sign-in screen, tap Resend [F1].
  2. Confirm the phone has Wi-Fi or cellular data and that Do Not Disturb is off [F1].
  3. Check that the phone is still signed in to the same Google Account under Settings > Passwords & accounts > Google [F1].
  4. Update Google Play services, because Google requires it for prompts on Android [F1][F2].
  5. If the prompt still does not arrive, use Try another way and choose another available method: another signed-in phone, backup number, backup code, hardware key, or passkey on another device [F2][F3].

For the rest of the same security path, continue with Google Account sign-in alert: what to check before changing your password, How to check Google Account devices and sign out suspicious access, How to Turn On Google Two-Step Verification on Android Without Losing Access, How to Generate Google Account Backup Codes and Recover Access Without Your Phone, and How to update your Google Account recovery phone and email without locking yourself out.

What has to be true for Google prompts to work

According to Google's Sign in with Google prompts help page, you receive prompts on any Android phone signed in to your Google Account [F1]. In the 2-Step Verification flow, Google also highlights four requirements that people often skip:

  • active internet access;
  • Do Not Disturb turned off;
  • updated Google Play services;
  • the phone still signed in to the correct account [F1][F2].

If one of those fails, the prompt may never show up even when your password is correct.

The right checklist before you spend a backup code

1. Resend the prompt

On the sign-in screen, tap Resend [F1]. It sounds obvious, but Google treats this as the first official fix, including for Request Expired cases.

2. Check connectivity and interruptions

Google says the phone must be connected to the internet through Wi-Fi or cellular data to receive prompts [F1]. It also says to turn off Do Not Disturb [F1].

In practice, confirm:

  • the phone can reach the internet normally;
  • airplane mode is off;
  • you did not mute or suppress key account notifications.

The practical point is simple: a Google prompt is not an offline SMS fallback. It depends on the signed-in device and Google's service layer.

3. Confirm the account is still signed in on the phone

Google's Android instructions say to open Settings > Passwords & accounts > Google and confirm the account is still there [F1]. If the phone was reset, the profile changed, or the account was removed, the prompt will not arrive because that device is no longer a valid destination.

This matters especially after:

  • switching phones;
  • resetting the device;
  • moving between personal and work profiles;
  • signing in to the wrong Google Account on the phone.

4. Update Google Play services

Google requires updated Google Play services for prompts on Android [F1][F2]. If that layer is stale or restricted, the problem may not be with your password or 2FA choice at all.

5. Check whether Google is asking for a stronger verification path

Google says the challenge you receive depends on what it thinks is best to protect the sign-in [F2]. That means a prompt may not arrive in the exact way you expect if the device, location, or risk profile changed.

For some sensitive actions, Google's help also says you may need:

  • 2-Step Verification enabled for at least 7 days;
  • a recovery phone added for at least 7 days;
  • your account signed in on a mobile Google or Gmail app for at least 7 days [F4].

That 7-day trust window explains a lot of frustration right after a phone swap or a rushed recovery setup.

When to use Try another way

If the prompt still does not arrive after that checklist, the correct move is not endless retries. Google explicitly tells users to tap Try another way or a similar option such as I can't do this [F1].

Official alternatives may include:

  • another phone signed in to your Google Account;
  • a backup phone number configured for 2-Step Verification;
  • a previously saved backup code;
  • a hardware security key;
  • a passkey created on another device;
  • a trusted computer where you previously chose not to be asked again [F2][F3].

My editorial inference from the primary sources is this: a backup code should be treated as emergency redundancy, not as the first reflex. If the prompt failed because of connectivity, account sign-out, or stale Play services, you can often recover the normal path without spending a finite backup method.

What Request Expired usually means

Google's prompt help says an expired request can mean:

  • there was an unsuccessful attempt to sign in to your Google Account;
  • or someone tried to use you as a recovery contact [F1].

If you were the one trying to sign in, resend the prompt [F1]. If you were not, treat it as a security review signal and move into the sign-in alert checklist.

If you lost your main phone

If the phone that normally receives prompts is lost, stolen, or unavailable, Google tells you to sign in another way and then review the account [F1][F2]. The main official fallback options include:

  • another signed-in phone;
  • a backup phone number;
  • a backup code;
  • a passkey on another device;
  • account recovery if none of those work [F2].

After you get back in, review:

Common mistakes that make this worse

  • spending a backup code before testing Resend, connectivity, and the signed-in account;
  • changing the password in panic before reviewing devices;
  • trusting a call, text, or email that tells you to approve a prompt;
  • removing the old phone before validating the new one;
  • relying on only one phone for every verification path.

Short checklist

  • [ ] I tapped Resend.
  • [ ] I confirmed active internet and Do Not Disturb off.
  • [ ] I checked that the account is still signed in on Android.
  • [ ] I updated or reviewed Google Play services.
  • [ ] I used Try another way only after that review.

Quick FAQ

Does Google prompt rely on SMS?

No. Google recommends prompts precisely because they are safer than SMS codes against phone-number attacks [F1][F2].

Can I use a backup code right away?

Yes, if it is the only option left. But the more efficient order is usually to test the prompt requirements first and only then use a backup code [F1][F2].

I changed phones today. Can that affect this?

Yes. Google documents trust windows of up to 7 days for certain sensitive checks and newer recovery-related signals [F2][F4].

When is this more than a technical glitch?

When a prompt arrives without you trying to sign in, when Request Expired appears without a clear reason, or when the failure comes with a sign-in alert, unknown device, or settings change you did not make [F1].

Sources

  • [F1] Google Account Help - Sign in with Google prompts (Android), verified September 3, 2026: https://support.google.com/accounts/answer/7026266?co=GENIE.Platform%3DAndroid&hl=en
  • [F2] Google Account Help - Turn on 2-Step Verification (Android), verified September 3, 2026: https://support.google.com/accounts/answer/185839?co=GENIE.Platform%3DAndroid&hl=en
  • [F3] Google Account Help - Fix common issues with 2-Step Verification, verified September 3, 2026: https://support.google.com/accounts/answer/185834?hl=en
  • [F4] Google Account Help - Verify it's you when you complete a sensitive action (Android), verified September 3, 2026: https://support.google.com/accounts/answer/7162782?co=GENIE.Platform%3DAndroid&hl=en

Editorial notes

  • Last editorial verification: September 3, 2026.
  • Menu names can vary by OEM, language, Android version, and account type.
  • This article combines official Google steps with explicit editorial inference about the most efficient order before using backup codes.