Crush+bug+telegram+upd

As of this writing, Telegram’s official bug tracker has acknowledged the “crush bug” with the label P1 (Critical) – Contact loop. A fix (upd v10.14.1) is in closed beta.

In a statement to beta testers on the Telegram Bugs channel, a developer wrote:

“We’ve identified the migration error from SQLite to MMKV affecting frequent contacts. The next update will include a quarantine script that bypasses the corrupted index.” crush+bug+telegram+upd

ETA for stable fix: 48–72 hours.

or

After digging through Telegram’s open-source TDLib issues and some obscure Reddit threads, you find others reporting the same symptoms:

“I see a message from my crush in the notification shade, but the chat is empty.”
“Their profile picture updates but the chat doesn’t sync.”
“UDP packets arriving out of order trigger an incorrect ‘message deleted’ event.” As of this writing, Telegram’s official bug tracker

One developer explains:

“If a Secret Chat session is initiated over UDP and the handshake is interrupted (bad MTU, firewall dropping UDP), the client may show a false ‘new message’ event. The actual data never assembles.” “We’ve identified the migration error from SQLite to

So your crush might have tried to send you a message — but a UDP bug ate it.

Or worse: a malicious “bug” (as in surveillance software) is interfering with UDP traffic to manipulate what you see.