0.97 RC1

[goatpig]

Is this testnet  or mainnet? I spend from these often on my own wallets. Is there something in the CppBridge logs? Or the terminal?

[nc50lc]

In mine, I've tested that in Regtest to see what's the previous post is about (since it doesn't seem to be related to his other posts).

About the logs,
There's no related error in CppBridge Terminal. Only that armorylog.txt line.
I've just reproduced it again with the same result and logs.

Sending without ticking "Create Unsigned" works without issues aside from a few seconds of lag.

[tomrobbo]

Mainnet. Terminal output when ticking "Create Unsigned":

Code:

  File "ui/TxFramesOffline.py", line 668, in update
    if self.ustx.signer.canLegacySerialize() and self.selectable:
  File "armoryengine/Transaction.py", line 168, in canLegacySerialize
    return self.signer.canLegacySerialize()
  File "armoryengine/CppBridge.py", line 1571, in canLegacySerialize
    reply = fut.getVal()
  File "armoryengine/CppBridge.py", line 116, in getVal
    raise Exception(self.data.error)
Exception: generic signer error message

Two things going on, I think:

1.The bridge answers CAN_LEGACY_SERIALIZE via replySuccess(result), so a "no" arrives as success=false and the Python side raises instead of returning False. That's looking like why the dialog never opens. I opened PR #789

2. With that fixed, the dialog opens but Legacy is greyed out (Claude says because canLegacySerialize() is just !isSegWit() (Signer.cpp:2593, and the "we dont allow legacy ser for SW txs" comment at 1338)

[nc50lc]

Mainnet. Terminal output when ticking "Create Unsigned":

Nice, it's the same error output in my other reply.
So I guess I've successfully reproduced it in my test yesterday despite merely guessing what the issue was.

BTW, there's a "/* NOTE: WIP */" comment near those lines so I guess the feature isn't finished yet.

[goatpig]

Will try to address your issues and PRs this weekend