Google Play Console Phone Number Verification Errors

Problem Statement

Developers verifying Google Play Console accounts encounter the error: We can't verify your phone number right now. Try again later. This occurs despite entering correctly formatted phone numbers, particularly affecting numbers with country codes like +7, +380, and +265.

The error blocks mandatory verification required for accounts created before September 2023, leaving developers unable to publish or update apps. Users report identical failures across multiple devices and networks, confirming it's not a local configuration issue.

Why This Error Occurs

Two primary technical errors cause this message:

1. HTTP 400 ("Precondition Check Failed")
   Indicates a temporary system-side failure with number verification for specific regions.

2. HTTP 429 ("Too Many Requests")
   Triggers after multiple failed attempts, locking the account for 1-15 days. Attempts from any number during this period will fail.

Underlying causes include:

• SMS/call quota exhaustion in your region
• Service disruptions targeting certain carriers
• Regional restrictions affecting "non-developed" countries

Solutions

1. Basic Verification Checks

Ensure compliance with standard Google requirements:

Format Rules

- Format: `+(Country code)(Area code)(Phone number)`  
  Example: `+14155552671` or `+441234567890`

• Try both SMS and voice call methods
• Switch between mobile and landline numbers
• Confirm proper signal strength
• Use incognito mode or clear browser cookies
• Wait 24-72 hours between attempts

2. Critical: Avoid Retry Loops

IMPORTANT

Stop all attempts if you see HTTP 400/429 errors! Each retry resets the lockout timer.

• HTTP 400: Wait 3 days minimum
• HTTP 429: Wait 7-15 days
• Monitor via browser console (F12 > Network tab)

3. Pre-register Phone with Google Account

A frequently successful workaround:

1. Add your phone number as both Recovery Number and 2-Step Verification in your primary Google account
2. Wait 12-24 hours
3. Attempt Play Console verification - now with SMS option typically working

Reports indicate ~80% success rate with this method

4. Alternative Number Strategy

If Step 3 fails:

1. Use a number from a "developed" country (US/UK/Germany/etc.)
2. Complete verification
3. Change number after verification:
   • Play Console > Settings > Developer Account > Contact details

5. Device Strategy

• Avoid desktop browsers - use Android devices instead
• Try cellular data instead of WiFi
• Attempt during off-peak hours (region-specific)

6. Contact Google Support

When all else fails:

1. Use official Verification Issues Form
2. Include:
   • Screen recording of failure
   • Specific error codes from browser console
   • Carrier/region details

Last Resort: Account Migration

If deadline imminent:

1. Create new developer account
2. Verify using solutions above
3. Transfer apps via Official Transfer Process
   ⚠️ Requires republishing apps! ⚠️

Regional Impact Observations

Country Code	Success Rate	Notes
+1 (US/CA)	High	Fewest reported issues
+44 (UK)	High	Voice calls often work
+49 (DE)	Medium	Requires waiting period
+7 (RU/KZ)	Low	High failure rate
+380 (UA)	Low	SMS capacity frequently issues

Best Practices Summary

1. Never spam retries - triggers 429 locks
2. Pre-register numbers as recovery/2FA first
3. Prioritize voice calls over SMS
4. Wait strategically between attempts (minimum 72 hours)
5. Document errors using browser console data

Deadline Notice

Unverified accounts risk suspension! Submit support tickets early if stuck.

Final Tip: Persistence pays off - most developers ultimately succeed by combining pre-registration with patient waiting. Multiple reports confirm Google is actively working on regional verification improvements.