You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[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
Request SMS verification repeatedly for one phone number until Firebase rejects it for quota.
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
vegeta2102 commentedon Sep 16, 2026
@demolaf
Can you check this issue ?
demolaf commentedon Sep 16, 2026
Hi @vegeta2102 , thanks for raising this issue. It has been fixed in PR #2509,
FirebaseUI-Android/auth/src/main/java/com/firebase/ui/auth/AuthException.kt
Lines 892 to 900 in b8b5531
vegeta2102 commentedon Sep 16, 2026
Thank you very much !
demolaf commentedon Sep 21, 2026
Closing this as resolved in PR #2509.
vegeta2102 commentedon Oct 2, 2026
@demolaf When will it be released?
github-actions commentedon Oct 2, 2026
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.
demolaf commentedon Oct 6, 2026
Hi @vegeta2102 , we're currently working on a new release. I'll keep you updated.