Failed trade; unable to open support; Cannot invoke "org.bitcoinj.core.Transaction.getLockTime()" because the return value of "bisq.core.trade.Trade.getDelayedPayoutTx()" is null

[ryenski]

Description

I have a failed trade for which I am unable to open a support request.

The trade failed with this message:

The peer's taker fee transaction is missing.
With out this tx, the trade cannot be completed. No funds have been locked. Your offer is still available to other traders, so you have not lost the maker fee. You can move this trade to failed trades.

The next screen says:

Open support ticket
Thre is an issue with a missing or invalid transaction.
Please do NOT send the fiat or altcoin payment.
Open a support ticket to get assistance from a Mediator.
Error message: Validation of Taker Tx returned: [Tx not found]

Clicking Open Support Ticket returns the following error:

Cannot invoke "org.bitcoinj.core.Transaction.getLockTime()" because the return value of "bisq.core.trade.Trade.getDelayedPayoutTx()" is null

Version

v1.7.5

Steps to reproduce

1. Trade is in a failed state
2. Click "Move trade to open trades" and click "Yes" to confirm
3. Click Open Trades.
4. Dialog pops up; click "Open Support Ticket"
5. Error is raised.

Expected behaviour

Support request is opened.

Actual behaviour

Error is raised:

Cannot invoke "org.bitcoinj.core.Transaction.getLockTime()" because the return value of "bisq.core.trade.Trade.getDelayedPayoutTx()" is null

Screenshots

Device or machine

MacOs 11.6 (20G165)
MacBook Pro (16-inch, 2019) 2.3 GHz 8-Core Intel Core i9

[boring-cyborg]

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

[ryenski]

Dialog displayed when moving trade to Failed:

[ryenski]

Dialog displayed when clicking the Attention icon in Open Trades:

[ryenski]

This dialog keeps popping up persistently while I'm trying to navigate around Bisq:

[ghost]

• Looks like a failed trade where no taker and deposit transactions were created.
• You can check if you have locked up funds by looking up the deposit tx address shown in the above screenshot. If there is no deposit transaction, your funds are not locked. The false error is known and being worked on.
• The problem of the persistent warning popup is addressed by PR 5771 due for the next release.
• A fix for the problem of opening a support ticket will be made shortly.

Thanks for reporting - Sorry for the inconvenience.

[ryenski]

Thank you. I'm not 100% sure I typed it in correctly, but bc1qy0q7gxxvm4wpgeym3sypj3728hyctz4a7rm0c3 does not appear to be used.

However I still appear to have 0.0162 BTC locked up in that transaction, which I can't close:

[ryenski]

The funds are listed under Locked Funds as well:

https://mempool.space/address/bc1qfuvtcv92evpm5p8um2u75kp2s6cyy8ddhv7xld6q38xg2m97wjgqux5px6

[ryenski]

• Looks like a failed trade where no taker and deposit transactions were created.

You're right that the taker transaction was not created, but I believe the deposit transaction was: https://mempool.space/tx/1c7a9cb978a4c9346110ff705e87e594e94e2e44fe668b9a1df8da23bf463ec1

[ghost]

Thanks for the context, your observations are correct and looks like your funds are locked. Its a very odd situation - please could you DM me your logs on keybase for further investigation & support.