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

Can't login to Telegram after update #1393

Closed
frozenspider opened this issue Dec 14, 2015 · 8 comments
Closed

Can't login to Telegram after update #1393

frozenspider opened this issue Dec 14, 2015 · 8 comments

Comments

@frozenspider
Copy link

I updated Telegram Desktop for Windows from 0.8.57 to 0.9.15 using downloadable installer, and now I can't login. Upon startup it briefly shows me my contact list, and then it's replaced by relogin screen prompting me for my phone number and confirmation code. After I input both, it once again shows me my contact list for a split second before returning me to login screen.
Tried to relogin 5 times already.
Reinstalling 0.8.57 back didn't help, neither did deleting tdata folder in Telegram install folder.
Here's the content of log.txt in Telegram folder:

[2015.12.14 06:49:36] App Info: reading settings..
[2015.12.14 06:49:36] App Info: reading encrypted settings..
[2015.12.14 06:49:36] Audio init time: 20
[2015.12.14 06:49:36] App Info: reading map..
[2015.12.14 06:49:36] App Info: reading encrypted map..
[2015.12.14 06:49:36] App Info: reading encrypted mtp data..
[2015.12.14 06:49:36] Map read time: 2
[2015.12.14 06:50:03] RPC Error: request 18 got fail with code 400, error AUTH_BYTES_INVALID
[2015.12.14 06:50:04] RPC Error: request 20 got fail with code 401, error AUTH_KEY_UNREGISTERED
@frozenspider
Copy link
Author

Any help?

@frozenspider
Copy link
Author

I ran it again for the first time after all this time and it suddenly worked. Could you please consider adding some additional logging to trace this problem in case it appears again?

@stek29
Copy link
Contributor

stek29 commented Dec 22, 2016

Have you experienced this issue again?

@frozenspider
Copy link
Author

No, but I haven't updated since.

@auchri auchri closed this as completed Dec 23, 2016
@frozenspider
Copy link
Author

So, you won't even consider adding logs? You don't consider this to be a reasonable request?

@stek29
Copy link
Contributor

stek29 commented Dec 25, 2016

@frozenspider Does Portable version work?

@frozenspider
Copy link
Author

Right now it does, but then again, so does the desktop version. Haven't tried it at the time bug was happening.

@github-actions
Copy link

github-actions bot commented Mar 9, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants