Firebase auth/too-many-requests Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Wait and stop retries

   Copy steps
   1. Pause for some time before trying again
   2. Add a debounce and a disabled state to the sign-in button
   Did this fix it? Yes No

2. 2. Use test phone numbers

   1. Firebase console > Authentication > Sign-in method > Phone > Phone numbers for testing
   Did this fix it? Yes No

3. 3. Test against the Auth emulator

   1. Run the Local Emulator Suite so automated tests don't hit production
   Did this fix it? Yes No

4. 4. Reset the user's password

   1. Send a password reset email so the user can regain access
   Did this fix it? Yes No

Symptoms

auth/too-many-requests, 'We have blocked all requests from this device due to unusual activity.'

Why it happens

• Repeated failed password attempts
• Loops that call sign-in or sendVerification repeatedly
• Phone auth testing with real numbers
• Automated tests hitting production Auth

This guide also covers

• auth/too-many-requests
• firebase blocked all requests from this device

The same problem in other apps

All not loading, error messages & connection guides →

• Supabase Max Client Connections Reached (Supabase)
• MongoDB Atlas Connection Timed Out (IP Not Whitelisted) (MongoDB Atlas)

Other Firebase errors

• Firestore Missing or Insufficient Permissions (permission-denied)
• Firebase auth/invalid-api-key Error
• Firebase auth/network-request-failed Error
• Firebase auth/operation-not-allowed Error
• Firestore Quota Exceeded (resource-exhausted)
• Firebase Unexpected Bill on Blaze Plan
• Firebase Cloud Messaging Notifications Not Received
• Firebase Deploy Failed (Functions and Hosting)