Open Dax89 opened 9 years ago
Same issue here
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 ../libqtelegram-aseman-edition/secret/decrypter.cpp, line 424
Some users reports crashes caused by an assertion that fails when using secret chats:
This is the interesting part of the log:
Looking at the Telegram documentation it seems that the server sends decryptedMessageActionRequestKey (0xf3c9611b) which is not handled.
More info: 1) https://core.telegram.org/schema/end-to-end 2) https://core.telegram.org/api/end-to-end/pfs 3) Bug report on my client (for complete log): https://github.com/Dax89/harbour-sailorgram/issues/10 4) https://github.com/Aseman-Land/libqtelegram-aseman-edition/blob/master/secret/decrypter.cpp#L414
Is there any way to handle that request?