I got logout by telegram

[Yuan-Chen Cheng]

I got hit by the following use case:

1. install channel: ubuntu-touch/stable/meizu.en, version version: 3 on mx4.
2. login to telegram account.
3. upgrade telegram
4. reboot or something
5. found I got logout from telegram
6. re-login and it look fine.
7. got logout again.

I didn't try to reproduce it, and certain procedure might not be exactly correct.

Still report to capture if someone else have similar issue.

[Michał Karnicki (karni)]

Logs contain:
401 AUTH_KEY_UNREGISTERED
(twice, and you mentioned you where signed out twice).

For reference:
https://github.com/Aseman-Land/Cutegram/issues/65#issuecomment-110225763
The assumption was the fault was on Telegram's end. I'll mark the bug incomplete, and we see if it happens more often. As it may have been on Telegram end, that would explain why reproducing the bug isn't easy.

[Michał Karnicki (karni)]

Reached out to TTF (Telegram Task Force). Since one of them also experienced such log out yesterday with a custom client software,
I asked them to comment here if they have more details. They would also let server folks know. Since the custom client was not C++, there's no common denomiator with that and our client, so may have been server side issue. I can't say that confidently yet, though.

[Shawn Wang (shawn111)]

I use MX4 ubuntu phone.
It can easy to reduplicate on my phone.

Don't need to update, change network.
Just send message and wait about 3 mins.

[Shawn Wang (shawn111)]

Telegram version: 1.3.20.113

[Ethan Chang (ethan.chang)]

I can confirm this issue with Shawn's steps.
1. Upgrade to 1.3.20.114
2. Launch Telegram
3. Send a message to another account
4. Wait for couple minutes
5. The telegram will be logout

[Shawn Wang (shawn111)]

Here is my telegram log.

/home/phablet/.cache/upstart/application-click-com.ubuntu.telegram_telegram_1.3.20.114.log

[Shawn Wang (shawn111)]

It seems not really logout from telegram.
The app still can receive the messages.

I can see it on the Notifications.

[Shawn Wang (shawn111)]

$ system-image-cli -icurrent build number: 81
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-08-06 13:41:21
version version: 81
version ubuntu: 20150806
version device: 20150709-8965e37
version custom: 20150716-819-8-42

Update to r81, still not fix this issue.

[Michał Karnicki (karni)]

Hi Shawn, ( /me back from hols)

I am not able to repro on r83 even after 10 minutes of sending the message. Would you be kind and do the following:

adb shell
touch ~/.config/com.ubuntu.telegram/.debug

rm ~/.cache/upstart/*telegram*

Then go ahead, reproduce the problem again, and attach the log please / or send it to my e-mail. Thank you.

[Michał Karnicki (karni)]

Actually I'll leave this as 'Confirmed', but I'd like to understand if Ethan / Shawn you guys are seeing the
401 AUTH_KEY_UNREGISTERED
in the logs as well. Can you still reproduce the problem? Is it reproducible every time or only now and then?

[Shawn Wang (shawn111)]

@Michał,

I'm not sure does r83 do any improve.
It seems r83 is harder to reproduce this issue.

I found once, after touch ~/.config/com.ubuntu.telegram/.debug

My system just upgrade from r83 -> r85.

Here is my log.

[Michał Karnicki (karni)]

Hi Shawn!

Kindly thank you for your log file. However, as mentioned on IRC, it does not contain reproduction of the problem.
Regarding r83, r85, etc, there have been no changes in Telegram recently, so the issue seems to be intermittent :S

[Ethan Chang (ethan.chang)]

the issue doesn't happen again after Install telegram v2.0.5.

[Michał Karnicki (karni)]

Thanks Etan. (FTR I'd call it 2.0.0.0-alpha1, anyone reading thi splease don't think there's 2.0.5 version out yet.)