Conversations stop updating after reconnection

[Alberto Mardegan]

This has happened quite a few times for me already:

1) Have Wifi on
2) Open telegram, open a conversation
3) Switch off wifi
4) Let the phone go to sleep
5) Receive a message in that conversation
6) Wake up phone
7) Reconnect to wifi
8) Wait for the notification about the incoming message (the one from step 5)
9) Unlock phone
10) Look at telegram: the conversation won't update

Notes:
- I'm not sure if steps 5 and 8 are needed, but they were present in all cases when I reproduced this bug.
- The input box becomes active after 1-2 seconds (in step 10), meaning that the connection is properly detected.
- In order to get back to a working state, one needs to go back to the main page of the app, and reopen the conversation.

Attaching the log file.

[James Lewis (james-fsck)]

Ive seen this issue, wasnt sure if it was telegram or OTA8

[James Lewis (james-fsck)]

Seems a bit more broad than the description above, ive noticed that if the telegram phone is locked when a message arrives, you will get a notification but switching to telegram app will never display the message.

[Michał Karnicki (karni)]

Marking as confirmed as affects multiple users.

[Michał Karnicki (karni)]

Note to self:

Consider these steps from (possibly duplicate) bug 1524307

Steps to reproduce:
1. Receive new message while phone is locked.
2. Unlock phone and swipe down message indicator
3. Press on the monochrome telegram icon next to the new message to open it in the app

[Jin (jindallo)]

I can not get any notifications from version 2.0.4.0,
need to check its mechanism in current code base or library.

[Randall Ross (randall)]

I can confirm this behaviour on:
flo - Nexus 7 (2013) Wi-Fi
Ubuntu 15.04 (r334)

If there is a temporary disruption in network connectivity (as happens frequently on mobile/wifi networks) then the device (flo) will disconnect and reconnect, but Telegram will only disconnect. There is no indication that Telegram is not sending/receiving messages. The only way to reconnect Telegram is to terminate the app and restart it manually.

[Michał Karnicki (karni)]

Yes, we have Jin looking into this whenever he's available.

[Roberto Mier Escandon (rmescandon)]

The behaviour that i've noticed is that the messages are not missed, but received after passed 2 or 3 minutes after the app comes to foreground again.

I tested the state of the QTcpSocket when not got the inmediate update and was QAbstractSocket::ConnectedState. Besides, the socket was marked as valid, open, readable and writable.

The socket is used to send a request to the telegram servers getting the differences (the updates) and QTcpSocket logs that the request is sent (N bytes written in the socket with no error), but no response is received.. until passed those 2 or three minutes