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
Implementing SMS code authentication, change phone number features or working on a bug (like this one firebase/flutterfire#4651) is difficult because after only a few (5?) login attmeps firebase is blocking the phone number for a certain time.
You are correct, the service will start to limit requests after a certain point. To get around this problem, during debugging or integration testing, we have FirebaseAuthSettings#setAppVerificationDisabledForTesting. This will bypass app verification checks and will skip sending an actual text message; instead you'll enter the code you pre-set in the Firebase Console. Just remember to turn this off before deploying :)
Implementing SMS code authentication, change phone number features or working on a bug (like this one firebase/flutterfire#4651) is difficult because after only a few (5?) login attmeps firebase is blocking the phone number for a certain time.
It seems this kind of limitation is not listed here: https://firebase.google.com/docs/auth/limits
Google "firebase auth too many requests" show a lot of result where develops are struggling with this issue.
The text was updated successfully, but these errors were encountered: