[bisq-network/bisq] Major errors happening when user tries to accept trade. (#2910)

spottedmarley notifications at github.com
Fri Jun 21 03:42:35 UTC 2019


This error has happened several times since version 1.0 but this is the first time I have had the opportunity to get a screen capture of the actual error dialog and the log file to go with. I have traded alot using bisq and this never used to happen before 1.0.

What is common to each time I've seen this issue is that I have several open "money order" trades that are in the "Payment started" faze and waiting for me to receive and confirm payment. Then someone tries to accept one of my open trade offers and I get flooded with errors: Please see attached screen shot of the error dialog and log file.

Here is the error that is copied to my clipboard: PeerAddress must not be null (sendEncryptedMailboxMessage)

When this error occures it tends to also corrupt my entire portfolio so that ALL of my trades are no longer listed. All my open trades and open offers are gone.

I have incremental backups of my data folder so I can recover from this but why does this keep happening? Like I said, it never happened until v1.0 and the DAO was turned on in the client.

![bisq-error-2](https://user-images.githubusercontent.com/2573814/59896012-db0d7780-93b4-11e9-96fa-446174229c12.png)
[bisq.log](https://github.com/bisq-network/bisq/files/3312911/bisq.log)



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2910
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190620/5dfd8769/attachment-0001.html>


More information about the bisq-github mailing list