Skip to content

[Auth-UI][v10.0.0-[beta05] SMS quota rejection maps to NetworkException, phone auth shows "check your internet connection" instead of "used too many times" #2513

Description

@vegeta2102

Steps to reproduce

  1. Request SMS verification repeatedly for one phone number until Firebase rejects it for quota.
  2. Enter that number and tap send.

Observed results:

「認証エラー / ネットワーク エラー。インターネット接続を確認してください。」 ( mean Please check your internet connection)
a network error, on a device with working connectivity. FirebaseUI iOS shows the correct 「この電話番号は何度も使用されています」(mean This phone number has been used too many times) for the same account state.

Expected results:

TooManyRequestsException, whose dialog message resolves to fui_error_too_many_attempts This is a string the library already ships translated in ja/ko/zh-rTW ("This phone number has been used too many times"). The correct copy exists and is simply unreachable.

Root cause:

Firebase reports SMS-quota rejection as FirebaseTooManyRequestsException, which extends FirebaseException notFirebaseAuthException.
AuthException.from only checks the ERROR_TOO_MANY_REQUESTS error code inside the is FirebaseAuthException branch, so the quota exception falls through to the catch-all is FirebaseException -> NetworkException. ErrorRecoveryDialog then renders fui_no_internet.

Is this possible to add FirebaseTooManyRequestsException -> TooManyRequestsException(...) before the is FirebaseException branch to fix this issue ?

Activity

  1. vegeta2102 commented on Sep 16, 2026

    @vegeta2102
    Author

    @demolaf
    Can you check this issue ?

  2. self-assigned this
    on Sep 16, 2026
  3. demolaf commented on Sep 16, 2026

    @demolaf
    Member

    Hi @vegeta2102 , thanks for raising this issue. It has been fixed in PR #2509,

    is FirebaseTooManyRequestsException -> {
    TooManyRequestsException(
    message = stringProvider?.errorTooManyRequests.nonEmpty()
    ?: stringProvider?.tooManyRequestsRecoveryMessage.nonEmpty()
    ?: firebaseException.message
    ?: "Too many requests. Please try again later",
    cause = firebaseException
    )
    }

  4. vegeta2102 commented on Sep 16, 2026

    @vegeta2102
    Author

    Thank you very much !

  5. demolaf commented on Sep 21, 2026

    @demolaf
    Member

    Closing this as resolved in PR #2509.

  6. vegeta2102 commented on Oct 2, 2026

    @vegeta2102
    Author

    @demolaf When will it be released?

  7. github-actions commented on Oct 2, 2026

    @github-actions

    This item is closed, so it may not receive regular attention.

    If it is still relevant, please open a new issue with an up-to-date reproduction, or open a new pull request.

  8. demolaf commented on Oct 6, 2026

    @demolaf
    Member

    Hi @vegeta2102 , we're currently working on a new release. I'll keep you updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions