Trade messages sometimes not being delivered

[suddenwhipvapor]

Opening this issue here by feedback from two different users. I asked if their issue was similar to #2925 but they reported it is not.
Pasting their comments fro the Bisq2 chat:

User 1:

disappearing messages were also a problem during the failed transaction that I mentioned. You might want to kick this up to whoever might be able to look into these things. I get that you need logs, screenshots, etc... but maybe a word of warning to devs would not go amiss. This seems like a fairly aggravating bug.

Trade proceeded and when I (buyer) confirmed that I had sent payment, seller's side remained unchanged. After further communication between me and seller, it was clear that some of my messages within trade window were disappearing, including from my side. Fortunately we were able to resolve matters in the private chat.

Not quite in my case. First, the problem isn't just the messages. There's still the issue of confirmation not appearing on the other party's side. Second, this is a question of messages disappearing rather than appearing later or in a different order.

User 2

Having a state change issue in a trade. Buyer pressed "Payment Sent" but the state did not change (at least for me). I don't have the bitcoin address to send to either, but buyer doesn't understand that. Mediator requested, but so far they do not understand either (sent a screen image in matrix, but I don't think they've seen it yet). This is really bad scenario.

It is basic english. I don't know what the problem is. Maybe he isn't seeing all my messages. I seem to be having problem just sending messages now too, it just says "Connecting to peer" on message status.

The issue is for some trades, we appear to be experiencing lost messages between peers. Including system command messages like signaling trade state changes and chat message.

There seems to be a limitation of the technology behind this platform that messages from one peer to another when the target peer is offline are queued somewhere, and once that peer comes online, delivered to them and removed from the queue. If for some reason the message gets lost at the peer before being added into the database, it's gone forever. The originating peer has no facility to verify if the messahe was actually received and to re-send if not.

[cparke2]

May be related or a duplicate of #2927