Hi!
I get an internal error, code 39 when using calling the verifyphone method of phone sign in. Can you give me any specifics, what causes this error? Is there a list?
Thanks a lot in advance!
Hi @pohpas
Could you please provide the contents of your pubspec.yaml, flutter doctor -v, and the relevant flutter run -v logs of the error?
Thank you
Getting the same issue.
I had the same problem then I knew what was this about, Error code 39 means that you've created too many credentials in a short period of time, you need to wait for a couple hours then try again and it'll work normally.
Ohhhh...
Then It should be mentioned in the documentation.
It is mentioned in docs
https://firebase.google.com/docs/reference/unity/namespace/firebase/auth
The "AuthError" Enum provides descriptions for all error codes. E.C. 39 is QuotaExceeded.
But is there a way to track the current usage of this quota
Could any of you please provide the full logs you get for this error?
Could any of you please provide the full logs you get for this error?
Unfortunately, this error only occurred when I ran the app in production mode with no debugging, sorry.
Well in any case the error message could probably be improved with at least a reference to the error code enum.
few users reporting this error recently.
my project is already in blaze plan.{
"error": {
"code": 503,
"message": "Error code: 39",
"errors": [
{
"message": "Error code: 39",
"domain": "global",
"reason": "backendError"
}
]
}
}
It is relating to sending too many request to firebase api from same ip address.You need to add your phone number to whitelist in firebase console
To add your phone number for testing your app type your number this section

But if you add your same banned number it will not accept that number.I suggest you wait to expire your spam or try it by another number
Most helpful comment
I had the same problem then I knew what was this about, Error code 39 means that you've created too many credentials in a short period of time, you need to wait for a couple hours then try again and it'll work normally.