Sending multiple invitations to the same peer can lead to the creation of "empty" duplicate conversations
## [Bug report] - Can you reproduce the bug: at will ## Steps to reproduce (STR): 1. Bob sends an invitation to Alice (conversation \#1) 2. Bob deletes his conversation with Alice and sends a new invitation (conversation \#2) 3. Alice accepts the new invitation At this point, things seem to be fine: Alice and Bob both see the same conversation (\#2) and can send messages to each other. 4. Alice and Bob close Jami 5. Alice and Bob restart Jami - Expected result: Alice and Bob still see conversation \#2 and can still send messages to each other - Actual result: Alice sees a message according to which the conversation is waiting for synchronization (this is for conversation \#1, though this isn't visible in the UI): ![image](/uploads/66185304819a8abf51f74f31f9873232/image.png) Bob sees an empty conversation (\#1) in which it's impossible to send messages (as shown in the video at #1794). 6. Alice deletes her conversation with Bob 7. Bob deletes his conversation with Alice 8. Bob sends an invitation to Alice (conversation \#3) 9. Alice accepts the invitation At this point, things again seem to be fine: Alice and Bob both see the same conversation (\#3) and can send messages to each other. 10. Alice and Bob close Jami 11. Alice and Bob restart Jami - Expected result: Alice and Bob have one functional conversation together (\#3). The deleted conversation (\#1) is no longer visible. - Actual result: Bob has two conversations with Alice: one that works (\#3) and one that's empty (\#1). Alice has two conversations with Bob: one that works (\#3) and one that's still shown as waiting for synchronization (\#1).
issue