Skip to content
Get a quote

Firebase Auth errorFirebase Auth: auth/quota-exceeded

auth/quota-exceeded is the Firebase Auth error when the project has used up a quota, such as the daily limit on phone sign-in SMS. Firebase lists 3,000 verification SMS per day for Firebase Authentication without Identity Platform.

Short answer

Compare the app’s SMS volume with the Authentication limits page to see which limit was hit. Move testing and App Review to fictional phone numbers, block bots before the SMS is sent, and upgrade to Identity Platform if real traffic needs more SMS per day.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why the quota runs out, and the fix

  1. 01

    Testing uses real phone numbers

    “Test phone number authentication without consuming your usage quota.” Firebase, Authenticate with a phone number (web)

    Every real test sends a real SMS. Add fictional numbers with fixed codes in the console and use them for development, QA and store review.

  2. 02

    Bots are triggering SMS

    A sign-in form that sends a code for any number attracts SMS abuse. Keep reCAPTCHA or App Check on, rate limit the send button, and set an SMS region policy that allows only the countries the app serves.

  3. 03

    Real traffic outgrew the daily limit

    Firebase lists 3,000 verification SMS per day and 900 per minute for Firebase Authentication. Upgrading to Identity Platform lifts the SMS limit.

  4. 04

    One number gets many codes

    “Additionally, there is a limit on the number of verification SMS messages a project can send to a single phone number within a set amount of time.” Firebase, Authentication limits

    Also check: Firebase also throttles codes sent to a single phone number. Heavy resending usually shows up as auth/too-many-requests instead; disable resend for a short time after each send.

Checked against the vendor’s docs on : Firebase docs: Authentication limits; Firebase docs: Authenticate with a phone number (web).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Firebase auth/too-many-requests · Firebase auth/invalid-app-credential · Firebase auth/invalid-phone-number · Firestore quota exceeded

Questions

More on this error

Does phone sign-in work on the Spark plan?

Not for real SMS. Firebase lists verification code SMS as Blaze plan only. Fictional test numbers send no SMS.

Do fictional numbers work in production?

Yes, but anyone who knows the number and code can sign in as that test user, so keep the list short and the accounts empty.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes