Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
White screen after server side logout #33
Comments
dfiloni
added
the
bug
label
May 4, 2017
Flohack74
added this to the 2.4.40 milestone
May 4, 2017
Flohack74
self-assigned this
May 4, 2017
Flohack74
added this to In Implementation
in telegram-app v2
May 30, 2017
Flohack74
moved this from In Implementation
to Discussion
in telegram-app v2
May 30, 2017
Flohack74
modified the milestones:
2.4.40,
2.4.41
Jun 7, 2017
Flohack74
modified the milestones:
2.4.41,
2.4.42
Jul 2, 2017
3arn0wl
commented
Jul 20, 2017
•
|
I'm experiencing the same issue, running the latest version - 2.4.41.1 - of the app on UBPorts Hammerhead. |
Flohack74
moved this from Discussion
to In Implementation
in telegram-app v2
Aug 31, 2017
Flohack74
moved this from In Implementation
to Implemented
in telegram-app v2
Sep 1, 2017
Flohack74
modified the milestones:
2.4.42,
2.4.43
Sep 7, 2017
balcy
commented
Sep 13, 2017
|
I'm using 2.4.42, but after being on unreliable networks in the train today, the app can no longer be started ( similar log file as reported above) and only shows a white screen. |
|
@balcy This is another story, we are talking specifically about a problem after logging out from telegram via menu, logging in again, or quitting the App before entering the code. Network issues are a known wekaness that can confuse the app. But can you check the logfile for "authCodeRequested" message? |
balcy
commented
Sep 13, 2017
|
oh ok I see, I was assuming the bug was for the white screen problem in general... |
balcy
commented
Sep 13, 2017
|
right now I cannot find it:
|
dfiloni commentedMay 4, 2017
•
Edited 1 time
-
Flohack74
May 4, 2017
When telegram-app is disconnected from the server, the app cannot start anymore, it shows a white screen instead of the login code request page (phone number is already known to app so this step is skipped).
How to reproduce:
The server will send the previous auth code again. So it looks like the server just thinks, ok code got lost, lets send it again. But the client does not change to the code input screen properly.
Log from affected user: