"Error: Identity key changed" when sending a second OMEMO message

1. You click on “lock” icon
2. Send message to User 1
3. Open other browser where you have loggedin User 1
4. You click on “lock” icon.
5. Send message to User 0
6. Try to send another and you got: Sorry, could not send the message due to an error. Identity key changed
7. You logout and try again, it is the same (all the time I have unchecked This is a trusted device ) I am trying this all day and every time it is the same. I used latest libsignal-protocol.js.

So as far as i can see Omemo does not work on converse.js. Hwo to debug this to checkout why?

<bountysource-plugin>

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[jcbrand]

@nikita-cerejo: Ok, that sounds like a different issue. Can you please create a new issue for this? You can just copy/paste the same data from this comment into it.

Sounds to me like Converse should be fetching the OMEMO bundle for user A, but isn’t.

[nikita-cerejo]

Thanks @jcbrand I am able to send encrypted messages when I changed my virtualhost domain from localhost to server.localhost. But I faced a scenario in this, which gives error that contact client doesn’t support omemo encryption. As shown in below screenshot(A).

Scenario : -> For the first time when contact is added, if user A (in my case Test 1 i.e [e-mail]) sent contact request to user B (in my case Test 4 i.e [e-mail]) and user B accepts it. -> If user B tries to send encrypted message first, it gives error that omemo encryption is not supported by user A client. -> But if user A sends encrypted message to user B first and then user B sends encrypted message then it works properly as shown in the screenshot(B). (Note : Test1 was logged in from chrome and Test 4 was logged in from microsoft edge browser)

screenshot(A) :

screenshot(B) :