Chat history in dispute is disappearing
See original GitHub issueclient 2.2.3, server 0.12.0
Dispute is open, I am the mod. Vendor opened dispute and buyer is MIA.
Go to discussion and send some comments.
Server log looks ok:
23:18:06.716 [SendMessage] [DEBUG] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw, etc…
Click away to any other UI view and then back, chat history is completely blank again:

Issue Analytics
- State:
- Created 5 years ago
- Comments:18 (8 by maintainers)
Top Results From Across the Web
Disappearing & reappearing chat history - Microsoft Community
I have 2 users in our organisation who chat through Teams, but when they click out of the chat it does not appear...
Read more >Turn history on or off in Google Chat - Android
In "Conversation Options," next to "History," tap On or Off. About history in spaces. When history is on. History is always on in...
Read more >3 times you should not use WhatsApp's disappearing messages
WhatsApp's disappearing messages self-destruct after seven days and while this is a great feature to have, it does have its issues.
Read more >Snapchat Settles FTC Charges That Promises of ...
Snapchat, the developer of a popular mobile messaging app, has agreed to settle Federal Trade Commission charges that it deceived cons.
Read more >Is it possible for a Facebook messenger conversation ... - Quora
Yes. The person who started the conversation could have deleted the conversation and it would disappear. Or one of the admins for the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@pinheadmz @webunraveling We’ve narrowed down this issue to a few causes.
The primary cause is currently, we show the message you’ve sent in the UI while it’s still in a sending state, but the server doesn’t record the message until it is successfully sent. If your node is unable to connect directly with the other node, sending the message can take a very long time.
If you do anything to refresh the view (such as closing the modal or reloading your app), the UI loses your pending message, and can’t retrieve it because it hasn’t been recorded by the server yet. This causes it to “disappear”, only to reappear later if you refresh the view again after the send has completed.
We’re going to fix this in #1532, but it’s not scheduled to be worked on until after we complete the multi wallet work in release 2.3.
There are probably some other issues involved here with messages, which we have on our radar to fix but they’ll be a pretty significant refactor of a few things. The short version is most users are behind firewalls or routers that block incoming messages, which makes them hard for other nodes to reach and communicate with.
You can make your own node easier to communicate with by forwarding your ports. You should also check any firewalls you’re running to make sure they’re allowing incoming messages for openbazaard.exe.
https://openbazaar.zendesk.com/hc/en-us/articles/360000282912-How-to-forward-ports-for-OpenBazaar
I’m closing this because the primary issue will be fixed in #1532