Inputs do not conform to this spec or are otherwise invalid

I’m getting this error when trying to sign the simplest transaction:

cardano-cli transaction build-raw \
    --tx-in 88d9225ff5d46b0efcd56dda20f2ea93b0a5fa232e7f70ab7d626746075a20d1#0 \
    --tx-out addr_test1qzymym7qc47kx65sjhntdl2prq85rj5v8mzv5pvyffnntz4el5zqnamef3yt2kprt866p5f38w6um6642lvzrj80d0xstnnmxq+10 \
    --tx-out addr_test1qzjlc05tyyw264wy7m4u7np5yqdwglks0xhu6765cl4qex9r9kvav4hmznru9px9n7cpa2hmmv4593eegve3t834xppqwskp4t+999823269 \
    --invalid-hereafter 369400 \
    --fee 176721 \
    --out-file tx.raw

It’s an alonzo-era transaction

[MartinSchere]

I created a toSpec helper function and it worked:

  public toSpec(txFilePath: string): string {
    const file = JSON.parse(readFileSync(txFilePath, 'utf-8'));

    const { cborHex } = file;
    const decoded = cbor.decode(cborHex);
    const newCborDecoded = [];

    for (let i of decoded) {
      if (Array.isArray(i)) {
        newCborDecoded.push(new Map());
      } else if (typeof i !== 'boolean') {
        newCborDecoded.push(i);
      }
    }
    const result = cbor.encode(newCborDecoded).toString('hex');
    return result;
  }

[alessandrokonrad]

Yes it’s possible. I’ll release a new Nami version soon, that also handles the additional bool in the transaction from the cardano-cli