Bug #3467
unreadable encrypted messages on startup
| Status: | New | Start date: | 06/08/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | v15 - AWESOME APP | |||
| Component: |
Description
Sometimes when ChatSecure starts, there are immediately messages from a contact delivered.
The problem is, they appear as "unreadable encrypted messages". Why are they even arriving if the user cannot read them? It is simply frustrating. At best the user is able to message the sending user back and ask them to re-send, an annoying process that, depending on the time of day/sending user's presence, may not even be possible.
It seems like maybe this problem has to do with initiation of encryption as ChatSecure loads. As a side note, I still don't see why ChatSecure, an app famous for secure communication efforts, even has an option for non-encrypted chat at all. Perhaps if encryption were the standard mode of startup (rather than a toggle the user must activate) this bug wouldn't happen?
also see Bug #3466.