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
I'm involved in a web app that uses tdLib to authorise Telegram users. I've worked users through the onboarding process. Some users do not receive the OTP from Telegram.
I have confirmed the phone numbers are correct, and sent in the correct format. In the application logs, successful and failed cases look identical. Real errors are being logged - eg. When Telegram returns the PHONE_NUMBER_BANNED exception.
In all cases I can see the authorization States passing from AuthorizationStateWaitTdlibParameters -> AuthorizationStateWaitPhoneNumber -> AuthorizationStateWaitCode.
Are there any other factors that anyone is aware of that would result in the users not receiving the OTP from Telegram?
The text was updated successfully, but these errors were encountered:
In cases where it works, the OTP appears within like 2-3 seconds. I've not encountered it showing up 10 minutes later. It either seems to work immediately, or not at all. Which makes me think that there is some factor I am missing.
I'm involved in a web app that uses tdLib to authorise Telegram users. I've worked users through the onboarding process. Some users do not receive the OTP from Telegram.
I have confirmed the phone numbers are correct, and sent in the correct format. In the application logs, successful and failed cases look identical. Real errors are being logged - eg. When Telegram returns the PHONE_NUMBER_BANNED exception.
In all cases I can see the authorization States passing from AuthorizationStateWaitTdlibParameters -> AuthorizationStateWaitPhoneNumber -> AuthorizationStateWaitCode.
Are there any other factors that anyone is aware of that would result in the users not receiving the OTP from Telegram?
The text was updated successfully, but these errors were encountered: