telegramdesktop / telegramdesktop/tdesktop

Randomly fails to update contents of chat - e.g. message deleted by bot remains visible in Telegram Desktop

Open
#27,353 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
33k
Forks
7.2k
Avg merge
1d 18h
Merged PRs (30d)
12

Description

Steps to reproduce

Obviously there's no way I'll ever be able to provide steps to reproduce.

This is what happens:

  1. In a supergroup, some user sends a message to the chat
  2. a bot that is admin of the chat, deletes the user's message almost immediately

EDIT: sometimes it also happens in this slightly different situation:

  1. the bot posts a message to the supergroup
  2. some time later, the bot deletes its own message
Expected behaviour

The deleted message should disappear in Telegram Desktop.
One may expect a delay of a few seconds at most.

Actual behaviour

Usually messages that are deleted by the bot (or by anybody for that matter) disappear as expected, but sometimes, randomly:
The message remains visible and never gets deleted in Telegram Desktop, unless I restart the application.

Messages that have been sent after the one that was deleted, are visible: so it's not like the connection has been lost or anything. The connection is working, the chat is syncing, but some particular update (i.e. the deletion of a message in particular) has been silently lost and never gets synced. And there's no indication anywhere that something is wrong. The user has every right to assume that what they are seeing is the current up-to-date contents of the chat, but that's not the case.

Obviously I checked in the mobile app in the same group and the message was deleted.

Operating system

Manjaro Linux

Version of Telegram Desktop

4.12.2

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is identified. Start by reproducing the bot-message deletion scenario in Telegram Desktop 4.12.2 and inspect the update-synchronization behavior when later messages still arrive. Done means deleted messages consistently disappear without restarting the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.