How to Fix Google 'A Notification Has Been Sent to Your Phone' Not Showing Up

When logging into your Google account, the webpage prompts "A notification has been sent to your phone," but your phone's notification bar, lock screen, and background remain completely blank with no response. This article organizes all possible solutions to fix this issue.

Symptoms

When logging into your Google account, the web page displays that a notification has been sent to your phone, but the phone shows no response at all. Clicking "Retry" does not work, and the login process gets stuck.

Solutions

The following solutions are listed in order of recommendation. We suggest troubleshooting them one by one.

Solution 1: Check Notification Permissions (⭐ Highly Recommended)

On many customized Android systems (especially Chinese ROMs), the notification permissions for Google and Google Play services are turned off by default, or users may have accidentally turned them off when clearing notifications. When permissions are disabled, Firebase Cloud Messaging (FCM) push messages can reach the client, but the system will not show any pop-up, causing the verification prompt to be "received but not displayed."

Enable Notification Permissions

The setting path varies across different phone systems:

If you cannot find Google Play services in the notification management list (it is hidden on some phones), try this path instead:

Settings → Apps → App management → Google Play services → Manage notifications → Allow notifications

Be sure to check the Google app using the same steps as well.

Force Stop Google Play Services

While notification permissions are disabled, the FCM push channel for Google Play Services may enter a suspended state. Simply enabling permissions might not automatically restore it. You need to manually force stop the service once to let it re-initialize:

Settings → Apps → App management → Google Play services → Force Stop

Once done, return to the Google login page and trigger the verification again. Your phone should receive the notification instantly.

Solution 2: Check Network and FCM Connection

Google's push service, Firebase Cloud Messaging (FCM), is blocked by default in mainland China. If your phone is not using a proxy or VPN, FCM cannot connect, and you won't receive the verification notification.

Self-Check Method:

• Can your phone open google.com normally? If yes, your proxy is working.
• Can Gmail or YouTube receive push notifications? If yes, your FCM connection is active.
• If you cannot connect, make sure your proxy/VPN is working properly, or use a router-level VPN/proxy for your Wi-Fi.

Additionally, even if your proxy is turned on, some domestic Android systems may restrict the background network access of Google Play Services individually under "Network permissions" or "Data usage control". Please check this in the app management settings.

Solution 3: Check Device Time

Google's push authentication relies on time synchronization. If your phone's system time differs significantly from the actual time, push messages will be discarded immediately.

Settings → System → Date & time → Enable "Set time automatically"
Or: Settings → Additional settings → Date & time → Use network-provided time

Ensure both "Set time automatically" and "Set time zone automatically" are turned on, and that the time zone is correct (China is GMT+8:00).

Solution 4: Disable Battery Optimization

Many aggressive battery-saving features will automatically kill background processes of Google Play Services, causing FCM connections to drop.

Settings → Apps → Google Play services → Battery → Unrestricted
Or: Settings → Battery → App battery management → Google Play services → Don't optimize

It is also highly recommended to apply the same settings to the Google app and Google Play Store.

Solution 5: Repair Google Play Services

If there is an issue within Google Play Services itself, FCM will fail to function properly. Try the following steps in order:

1. Clear Cache: Settings → Apps → Google Play services → Storage & cache → Clear Cache
2. Uninstall Updates: In the same menu, tap the three dots in the top-right corner and select "Uninstall updates". This will roll back to the factory version. You can then manually search for Google Play Services on the Play Store to update it to the latest version.
3. Restart your phone

Solution 6: Still No Luck? Use Alternative Login Methods

If you have tried all the above solutions and still cannot receive the push notification, there is no need to get stuck. Google's two-step verification page provides alternative methods that allow you to log in without waiting for a push notification:

• Security Key: Use a physical hardware key (YubiKey, Titan, etc.) or your phone's built-in security key feature to verify via USB, NFC, or Bluetooth.
• Security Code: Get a 10-digit offline security code directly from your phone and enter it to log in.

Steps to Get an Offline Security Code:

You can generate security codes directly from any Google app where you are already signed in. This process does not require an active internet connection, and each code is valid for 15 minutes.

1. Open any Google app on your phone (Google Play Store, Gmail, or the Google search app).
2. Tap your profile picture in the top-right corner → "Manage your Google Account".
3. Go to the "Security" tab.
4. Scroll down, find "Security code", and tap it.
5. After verifying with your fingerprint or password, two 10-digit codes will be displayed. You can use either of them.

If the codes expire, just repeat the steps to generate new ones.

Using a Security Key:

If you have a FIDO2 / U2F hardware security key, or if your phone supports the built-in security key feature (Android 7.0+), choose the "Security Key" option and follow the on-screen instructions.

Configure More Backup Verification Methods in Advance:

Go to Google Account Security Settings to add the following backup verification options to avoid being locked out next time:

• Google Authenticator: Scan the QR code to bind and generate 6-digit offline verification codes that refresh every 30 seconds. When logging in, select "Try another way" to use this authenticator.
• Backup Codes: Generate ten 8-digit backup codes. Each code can only be used once, but they are permanently valid. We recommend printing them out or taking a secure screenshot.
• Passkey: Set up a passkey using your fingerprint or face unlock. This allows you to verify via biometrics directly, bypassing both password and two-step verification prompts.

Summary

This article is published by toolshu, feel free to share it with anyone experiencing similar issues.