Andrzej Wójcik (Tigase) opened 5 months ago
|
|||||
Referenced from commit 5 months ago
|
|||||
Andrzej Wójcik (Tigase) changed state to 'In Progress' 5 months ago
|
|||||
Andrzej Wójcik (Tigase) changed state to 'In QA' 5 months ago
|
|||||
I've found that |
|||||
Andrzej Wójcik (Tigase) added "Related" tygrys/tygrys#218 5 months ago
|
|||||
Artur Hefczyc changed state to 'In Progress' 5 months ago
|
|||||
Still not working. Details in tygrys/tygrys#219 |
|||||
@kobit This issue is fixed as it was about not decrypting Message Carbons messages at all (basically resulted always in an error with message about OMEMO not being supported by device. Now the issue is about incorrect decryption (or rather errors with decryption) and not not decrypting messages at all. |
|||||
Ok, in such a case, please close this issue and reopen a new one for the specific error. |
|||||
Andrzej Wójcik (Tigase) changed state to 'Closed' 4 months ago
|
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
none
|
Sprints |
n/a
|
Customer |
n/a
|
Issue Votes (0)
OMEMO encrypted messages delivered by Message Carbons are not decrypted by the library, instead default/fallback body is being reported and message is left encrypted.