Google Meet Direct Calling Glitch: Why You Can't Reach Contacts
Many Google Meet users rely on its direct calling feature to quickly connect with contacts. However, a recent thread on the Google support forum highlights a frustrating issue where users are suddenly unable to make these direct calls, receiving the message: "You're calling someone who can't receive calls. Share a Meet link instead." This problem has left many wondering why their trusted communication tool is failing.
The Google Meet Direct Calling Glitch: What Users Are Experiencing
The core of the problem, as described by User 16490394342552565736, is a sudden inability to call any contact via Google Meet. Despite both parties having updated apps and clear caches, the error persists. Interestingly, while the user can't initiate calls, they can often receive calls from the same contacts. Adding to the confusion, incoming calls might ring on other linked devices (like Google Home or a Pixel tablet) but not on the primary phone, even a high-end device like a Pixel 10 XL Pro.
Another user, User 11792576419945463057, echoed similar sentiments, noting that the issue could be selective – working for some contacts but not others, even with identical app versions and verified phone numbers. SamZAk also reported the same issue, specifically linking it to a recent Google Meet application update, suggesting a potential widespread google meet bug report scenario.
Potential Causes and Troubleshooting Steps
A Google Meet apps Help Community expert, ShrutNM, provided several key insights and troubleshooting steps, suggesting the issue is often related to account or device settings rather than a simple app bug, though recent updates might trigger underlying conflicts.
1. Account Sync and Device Prioritization
If calls are ringing on your Home devices or tablet but not your phone, your Google account might be prioritizing another device for Meet calls. ShrutNM advises:
- Check Notifications: Ensure Google Meet notifications are fully enabled on your Pixel phone and not restricted by battery saver settings.
- Active Device: Verify your phone is selected as an active device for your Google account.
- Account Refresh: Remove your Google account from your phone, restart the device, and then add the account again. This can often resolve sync-related glitches.
- Meet Calling Settings: Confirm that Meet calling is enabled within your account settings. If disabled, direct calls will not work.
2. Multiple Account Conflicts
For users managing both work and personal Google accounts on the same device, account conflict is a common culprit. ShrutNM recommends:
- Switch Accounts: Open Google Meet and ensure you are switched to your personal account (the one intended for calling).
- Verify Calling Enabled: Double-check that Meet calling is enabled for that specific personal account.
- Temporary Workaround: Try signing out of your work account temporarily, or even remove it from the device, and then test calling again.
- Clear Cache: Go to your phone settings, clear the cache specifically for the Google Meet app, and restart your device. After restarting, open Meet with only one account active and attempt the call.
The Resolution: Sometimes It's a Temporary Glitch
Interestingly, the original poster, User 16490394342552565736, reported that the issue resolved itself after a few days without any specific intervention, suggesting it might have been a temporary server-side glitch or a transient google meet bug report that was silently patched. However, for others, the problem persists, especially after recent updates, indicating that the troubleshooting steps above remain crucial.
While the exact cause can vary, these insights from the community and experts provide a clear roadmap for resolving the "can't receive calls" error in Google Meet. If the problem persists, documenting your steps and providing a detailed google meet bug report to Google support is the next logical step.