App crashes on startup (ASSERT with many x == (qint32)DecryptedMessageAction::[...])

[Christoph Schulz]

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)]

Thanks so much Christoph. I'm marking this as duplicate, but copying your bug report body content to the other one.

If you don't mind loosing your secret chats, you can do this workaround (note this will remove your secret chat history!):
on the phone (terminal app) or via adb shell from your computer:
rm -rf ~/.config/com.ubuntu.telegram

If you do care about secret chat contents, don't do what I said above, please wait for an update..

[Christoph Schulz (ch-schulz)]

Hello,

updated to OTA 9.1 yesterday (today night :D) and now everything works fine again, even notifications (turned them to "on" in Telegram Settings; not even got the initial dialog asking me for notifications).

Also can remember it worked earlier before OTA 9.1, but hadn't my credentials in mind and forgot to submit later :/

But anyway: Strange? :)

[Michał Karnicki (karni)]

No, not strange, you're just not in the state that caused the bug, the problem is still there though. Thanks for checking!