conversejs / converse.js

Web-based XMPP/Jabber chat client written in JavaScript
http://conversejs.org
Mozilla Public License 2.0
3.09k stars 776 forks source link

No message reception in Converse after an OMEMO message has been sent #1237

Open MotoGP-Fan opened 6 years ago

MotoGP-Fan commented 6 years ago

Tested with: Converse 4.0.2 Prosody 0.10.2 on Debian 9.5

Firefox & Chrome (both current releases)

Setup Converse with non minified css, js and libsignal-protocol

Perhaps similar to: https://github.com/conversejs/converse.js/issues/1193

Issue: No message reception in Converse after an OMEMO message has been sent with Converse. Issue tested with Converse and Conversations (2.3.1 +pcr) with blind trusted keys enabled.

Description: If you have an account with more than one device connected to the XMPP server receiving messages will no longer work after the first OMEMO message has been sent in Converse. Even switching from OMEMO to plain text does not change this.

Conclusion: If you want to receive OMEMO encrypted messages in Converse you have to make sure that you are exclusively logged into Converse with that account.

Notice: To receive OMEMO messages in Converse it is necessary that you first send an OMEMO message to the contact from which you want to receive encrypted messages.

If you are logged in with more than one device the attached error message appears in FF browser:

Error-log_converse-omemo.txt

--- Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/64431623-no-message-reception-in-converse-after-an-omemo-message-has-been-sent?utm_campaign=plugin&utm_content=tracker%2F194169&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F194169&utm_medium=issues&utm_source=github).
jcbrand commented 6 years ago

Great bug report, thanks.