-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AssertionFailedError on startPhoneVerification #52
Comments
I have the same problem.when I sent to CN , it I have to wrap node-authy api. |
Any update on this issue? I have the same problem with IE, UK.
|
These validations will have to be relaxed then. You would expect a boolean which is referenced on their API docs to either be true or false 🤷♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happens for around 100 different numbers each day from many different countries (CA, FR, AU)
Sometimes carrier is null, sometimes it is not there at all, sometimes is_phonenumber is missing.
Example:
and another one:
This might have something to do with:
https://support.twilio.com/hc/en-us/articles/360004563433
The text was updated successfully, but these errors were encountered: