-
Notifications
You must be signed in to change notification settings - Fork 8
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
Unable to store Telegram account when two-step verification is enabled #134
Comments
@PromiseFru When is this prompt made? Does the gRPC return a method to help know the password is required? If yes please share that thanks |
@sherlockwisdom, the prompt occurs at the code exchange level. After exchanging the code for the first time from Telegram, if two-step verification is enabled, the user is prompted for the password they set for two-step verification and the same verification code initially sent. The publisher provides the |
@PromiseFru Thanks, does the Telegram API provide any means of knowing if account requires a password? |
No, the Telegram API does not provide a direct way to determine if an account requires a password for two-step verification. You'll only find out at the code exchange level when the user is prompted for the password if two-step verification is enabled. |
Relying on failure to determine if password is a hack, we should use a 2 step then to solve it. Please let me know when we have one so the apps start integrating |
@sherlockwisdom, the publisher now indicates whether 2-step verification is enabled in the https://github.com/smswithoutborders/SMSWithoutBorders-Publisher/blob/main/docs/grpc.md#response-4 |
The RelaySMS app fails to prompt for the required password when storing a Telegram account with two-step verification enabled. Instead, it repeatedly outputs the following error:
Steps to Reproduce:
Expected Behavior:
An input field should appear to allow the user to enter their password when two-step verification is enabled on their Telegram account.
The text was updated successfully, but these errors were encountered: