Bug: Added transactions via API -> Cannot load 'Transactions' page

[rasheedja]

I was experimenting with the API and platform on preprod for a service we're building.

I tried submitting some transaction via CLI, this seems to have worked, I was able to sign the transaction with the required wallets.

I cannot, however, load the 'transaction' page.

I did some further testing, I created an unsigned transaction, and pasted the hex into the 'Signing' page, here, I was able to sign it with other wallets, but when trying to import the signed transaction CBOR, I get an 'Import Failed' error, with the message 'Failed to deserialize transaction CBOR'.

So, my instinct is that for whatever reason, the transaction I added via API has a CBOR that cannot be deserialized, and that's causing the 'Transactions' page to break. This also locks up whatever UTXOs were being used in that transaction. Note that the CBOR itself is valid, it's a 4-element structure with the actual tx in the 3rd element, maybe the platform expects it in a certain format?

To unblock someone in this situation, either the API should reject the transaction, or the frontend should let me 'reject' the transaction to unlock the UTXOs, or the API should have an endpoint to 'reject' a transaction.

Some details:

• network: preprod
• wallet with 2 'bad' transactions: cmmoyccbt0003le04veswn9b5
• wallet with 1 'bad' transaction: cmmuuxyg40001l204bmcb6jim
• wallet with no 'bad' transactions, but 'bad' cbor in 'Signing' area (cannot be imported): cmmuv088r0002jl04zjq10vtn

Let me know if you need any more info. I could share a CBOR if that helps.