When I try to send first OMEMO message, Beagle collects keys. If this process takes more time (remote recipient server), input field is locked, nothing happens. It looks like I didn't press enter button, then I press it again and again.
When Beagle prepares keys, then it sends message from input field as many times as I pressed enter button.
Andrzej Wójcik (Tigase) commented 5 years ago
This issue is slightly more complicated as we need to deal with sending OMEMO messages in order and at the same time wait for session creation which sometimes requires access to other servers over S2S. I've decided to work on a more complex solution that will queue messages, display them as unsent until they are sent and allow "queueing" messages even when the client is disconnected. This will make usage of BeagleIM over a not very reliable network a lot easier and better.
Andrzej Wójcik (Tigase) commented 5 years ago
Those changes lead to changes in handling error messages and changes in marking unread messages
Bartosz Małkowski commented 5 years ago
I tried to send encrypted message. It was queued as "unsent" and after while Beagle crashed.
When I try to send first OMEMO message, Beagle collects keys. If this process takes more time (remote recipient server), input field is locked, nothing happens. It looks like I didn't press enter button, then I press it again and again. When Beagle prepares keys, then it sends message from input field as many times as I pressed enter button.