New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
MotoGP-Fan opened this Issue Oct 8, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@MotoGP-Fan

MotoGP-Fan commented Oct 8, 2018

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: #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

@jcbrand

This comment has been minimized.

Member

jcbrand commented Oct 8, 2018

Great bug report, thanks.

@jcbrand jcbrand added the bug label Oct 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment