Skip to content
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

[BUG] #376

Open
philpetrov opened this issue Nov 22, 2024 · 0 comments
Open

[BUG] #376

philpetrov opened this issue Nov 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@philpetrov
Copy link

Describe the bug
Cant authotize with test accounts

To Reproduce
Steps to reproduce the behavior:

  1. Up local tweb
  2. Go to test env http://localhost:8080/?test=1.#/login
  3. Input number +9996621111
  4. Input code 22222

Expected behavior
Authorized

Screenshots
Invalid code

Additional context
Why test acciunts not working?

"If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part)."

https://core.telegram.org/api/auth#test-accounts

@philpetrov philpetrov added the bug Something isn't working label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant