Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OMEMO - older messages are lost
See original GitHub issueHEAD (0a7dff442c7bc1e1a13668ea27a5f9e764b9edf3), Firefox 80, using IndexDB
To Reproduce Steps to reproduce the behavior:
- login
- send or receive messages in 1:1 or MUC, with OMEMO
- logout
- login
Expected behavior Older messages are available
Actual behavior
All past messages (both from me and my contacts) are replaced with I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo
Moreover in 1:1, all the messages are deleted, only the last one is kept, but it’s actually the string above.
Sometimes some messages (eg. pulled from MAM if Converse was offline) are not corrupted, but on the next login they’ll be.
Note: key is NOT regenerated on login.
Related to: https://github.com/conversejs/converse.js/issues/2235
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:28 (27 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Right, totally makes sense to me now. Thanks (and sorry for side tracking the topic)!
Closing in favour of https://github.com/conversejs/converse.js/issues/2733