Telegram crash in decryptedmessageaction - must catch up with secret chat API 20

Bug #1512332 reported by Michał Karnicki
134
This bug affects 28 people
Affects Status Importance Assigned to Milestone
Telegram app
Confirmed
Critical
Unassigned

Bug Description

We have a crash in decryptedmessageaction, because we're missing handling of API 20 end-to-end:

https://core.telegram.org/schema/end-to-end

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

Sample crash log available in this bug report (duplicate):
https://bugs.launchpad.net/telegram-app/+bug/1524094

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

By Christoph:

Since since friday (12.2.) my Telegram App crashes immediately after startup (I see my chat list and then it crashes).
This is the last message written to the the Telegram logfile in .cache/upstart:
ASSERT: "x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionSetMessageTTL || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionReadMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionDeleteMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionScreenshotMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionFlushHistory || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionResend || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionNotifyLayer || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionTyping" in file ../secret/decrypter.cpp, line 421

App Version 2.0.4.0
OTA-9 (20160123.1)
Aquaris E4.5

Michał Karnicki (karni)
summary: - Telegram v2 should catch up with secret chat API 20
+ Telegram crash in decryptedmessageaction - must catch up with secret
+ chat API 20
Revision history for this message
Michał Karnicki (karni) wrote :

Specifically, libqtelegram-aseman-edition (upstream) needs to handle:

decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

Revision history for this message
flohack (flori-bin) wrote :

For some strange reason it works for me now, after latest OTA-9.1 update? Was smth pushed out?

BR

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

At this moment I can't tell for sure, upstream may have fixed it. Let's leave it be here for now.

Revision history for this message
Pascal Krause (krapas) wrote :

I have same issue on Aquaris E5 OTA-9.1, Telegram 2.0.8.1.
Issue was present. After some time it worked again but now it is broken again.
My assumption here, it depends on received messages. It got broken again, right after I received a message on secure chat.
Here the ~/.cache/upstart log:
[20160307 19:41:42.736 CET ASSERT: "x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionSetMessageTTL || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionReadMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionDeleteMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionScreenshotMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionFlushHistory || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionResend || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionNotifyLayer || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionTyping" in file ../secret/decrypter.cpp, line 424

Revision history for this message
Jin (jindallo) wrote :

I confirmed this issue since our member just met this symptom,
let's monitor this problem and this task will be scheduled.

Changed in telegram-app:
status: Triaged → Confirmed
Revision history for this message
Oliver Laub (oliver-laub) wrote :

Since I use encryption my Telegram crashes regularly.
First appearance was when someone sent me a secret message with an included sticker. Wiping the Telegram message folders via terminal app helped.
2 days ago someone sent me a message and now Telegram crashes after showing 1 second the chat overview. No crash reports is sent automatically.

If you need logs or trace files, please tell me how to create them or where to find ...

Hardware: BQ Aquarius E4.5
OS: Ubuntu 15.04 (OTA-14)

Revision history for this message
flohack (flori-bin) wrote :

Jin, is there any update on this? The original reporter did this bug report over one year ago, for an App like Telegram I think its mandatory to closely follow API changes from upstream. Otherwise people get annoyed and will abandon not only the App but also Ubuntu Touch in general.

Revision history for this message
Joolz (joolz) wrote :

After the big upgrade that added a lot of funtionality this bug was still present.

/me purged Telegram a week or so ago, good riddance.

Revision history for this message
flohack (flori-bin) wrote :

Hello All,

I managed to mitigate the crashes for about 90% of them. If anyone is interested, telegram-app continues development in the UBports hemisphere. Last version is here: https://openstore.ubports.com/app/com.ubuntu.telegram, Github: https://github.com/yunit-io/telegram-app - you may test & report bugs on GH please :)

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.