Messages are getting lost

Bug #1449685 reported by Michael Zanetti
94
This bug affects 19 people
Affects Status Importance Assigned to Milestone
Telegram app
Fix Released
Critical
Michał Karnicki

Bug Description

Version 1.3.4 (101)

I keep on losing messages. I have a feeling this happens because I'm using the desktop app. If the phone is in deep sleep mode, offline or the telegram app closed, and an incoming message is picked up by the desktop client, chances are quite high that this message won't ever show up on the phone app.

I've attached two screenshots, one from the desktop app, the other from the phone app. Notice how the phone app is missing the whole conversation from 13:37 to 18:12

There is one hour time difference on those screenshots because I'm travelling and I didn't change the phones time zone. However, I have this issue all time when beoth devices are in the same time zone too.

Tags: v2-verify
Revision history for this message
Michael Zanetti (mzanetti) wrote :
Revision history for this message
Michael Zanetti (mzanetti) wrote :
Michał Karnicki (karni)
Changed in libqtelegram:
status: New → Confirmed
importance: Undecided → Critical
Michał Karnicki (karni)
Changed in libqtelegram:
assignee: nobody → Michał Karnicki (karni)
milestone: none → m23
status: Confirmed → In Progress
Revision history for this message
David Planella (dpm) wrote :

It's exactly the same issue I mentioned a while ago, I keep losing messages too. The only workaround is to manually clear the phone app's data and then get Telegram redownload all the messages.

Michał Karnicki (karni)
Changed in libqtelegram:
milestone: m23 → m24
Michał Karnicki (karni)
Changed in libqtelegram:
milestone: m24 → m25
Revision history for this message
Michael Zanetti (mzanetti) wrote :

This keeps on happening, even if the Desktop app is not running somewhere.

tags: added: v2x
Changed in libqtelegram:
status: In Progress → Confirmed
Michał Karnicki (karni)
tags: added: v2
removed: v2x
Revision history for this message
Ethan Chang (ethan.chang) wrote :

Tried telegram v2.0.5 , the issue didn't happen again.

Revision history for this message
Jos van Houtem (jos-vh67) wrote :

Hi.
I am also loosing parts of the conversation.
In my case this happens because I do have bad 3G reception at home. So I receive a signal that there are new messages (sound and LED), I can check the preview, I check the app logo in the side pane and it shows (for instance) 3 messages. I open the app and nothing happens. When I get reconnected to 3G, the original 3 messages do not reload, I can only read new added messages.
I'm using BQ 4.5 and the latest Telegram app from the Ubuntu Store (1.3.20.114)

Revision history for this message
Yuan-Chen Cheng (ycheng-twn) wrote :

@Jos, we knew this issue happened in v1.x. We are currently working on refactoring the code and plan to release v2.x. Current we are still in pre-alpha stage for v2.x. The test in #5 is against v2 pre-alpha version.

Michał Karnicki (karni)
tags: added: v2-verify
removed: v2
Michał Karnicki (karni)
Changed in telegram-app:
milestone: m25 → alpha1
Revision history for this message
Michał Karnicki (karni) wrote :

Due to the fact we moved to re-using TelegramQML (engine of Cutegram), we expect this bug is no longer reproducible. Should we have a single instance of that, we would revisit the bug.

Changed in telegram-app:
status: Confirmed → Fix Committed
Revision history for this message
Michael Zanetti (mzanetti) wrote :

confirming that I have not seen this happening with telegram 2 preview packages any more. I did see some struggles with syncing messages on very poor data connections, but it recovered fine as soon as the network connection got better.

Revision history for this message
Marco (jermy-07) wrote :

Is there an eta of the fixed version of telegram? Right now I estimate to miss more than 1 % of all messages (both picture and text messages) which makes things wore when you are expected to react to those messages.

Revision history for this message
Michał Karnicki (karni) wrote :

Hi Marco, I'm terribly sorry. Regarding the upcoming update date, this has changed a few times as we had to resolve some issues on the way (often platform ones around the app itself), but I'm already working on the last bit, which is upgrade code from Telegram v1 to v2. This should be completed in 1.5 week, plus QA. Conservative estimate would be 3 weeks..

Revision history for this message
Marco (jermy-07) wrote :

Awesome! It's great to see things moving forward. I will test the new version as soon as the update is available.

Michał Karnicki (karni)
Changed in telegram-app:
status: Fix Committed → Fix Released
Revision history for this message
Iulian Onofrei (revolteh) wrote :

It still happens for me quite often. Most often in groups with many (500+) unread messages. The only way I managed to get them back was by clicking on a quoted message of a reply, while the quoted messages was missing, so it scrolls to a white "page" and then loads some messages near it. It happens on the iOS and the Mac client too.

Revision history for this message
vitor torres (vitor7hgt) wrote :

“Most often in groups with many (500+) unread messages. The only way I managed to get them back was by clicking on a quoted message of a reply, while the quoted messages was missing, so it scrolls to a white "page" and then loads some messages near it. It happens on the iOS and the Mac client too.”
This new bug happens all the time! 2k unread messages groups looks like 300~500 unread messages when scrolling. The only way to get some messages back is to click on quoted messages, so the chat scrolls up to a blank part and download around 100 messages. Pls fix it.
Device Information: Device: iPhone8,2; iOS Version: 11.2.2 App Version: 4.7.1

Revision history for this message
vitor torres (vitor7hgt) wrote :
Revision history for this message
vitor torres (vitor7hgt) wrote :

I added a video trying to show what happens

Revision history for this message
Michał Karnicki (karni) wrote :

Vitor, you have commented on a 2-year old bug report for Telegram app for the *Ubuntu* platform. (Canonical has stopped the development of the mobile platform.)

If the bug is on iOS, you should find an appropriate place on GitHub to file the bug report. Please do not comment here as a number of people will be notified via e-mail about a bug for a project that no longer is even valid. Thank you.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.