script.toBytes() returning empty bytes

[v4v2]

Describe the bug

The toBytes() method of Script is returning empty array on Signet.
I am using a port of BDK to typescript.

To Reproduce

  const inputs = await transaction.input()
  for (const index in inputs) {
      const input = inputs[index]
      const script = await input.scriptSig.toBytes() // THIS IS EMPTY
      input.scriptSig = script
      vin.push(input)
    }
// more ... code

the inputs is an array of TxIn with the fields sequence, previousOutput, witness, but the sigScript which is of type Script is returning empty bytes.

Expected behavior
Get the input script as bytes or hex.

Build environment

• BDK tag/commit: (how to figure out? I guess it is the latest....)
• OS+version: ArchLinux latest (using kernel 6.x)
• Rust/Cargo version: 1.83
• Rust/Cargo target: x86_64-unknown-linux-gnu

Additional context
Signet

Thanks in advance 👍

[v4v2]

if this is indeed a bug and not a misuse from my part, I offer help to fix 👍

[notmandatory]

You said you're using a port of BDK to typescript, which project is that?

[v4v2]

@Psycarlo please help me explain how we are using BDK in typescript in our project

[Psycarlo]

We are using bdk-rn

[Psycarlo]

Our app is crashing trying to build a transaction.
Looks like it crashes when using addRecipient

transactionBuilder.addRecipient(script, amount) // TODO: crashing here

Script is being created like this:

const address = await new Address().create(recipient) // recipient is the address string
const script = await address.scriptPubKey()

[Psycarlo]

Silly me

When I was building the transaction, I was not awaiting.
For example,

transactionBuilder.feeAbsolute(fee)

instead of

await transactionBuilder.feeAbsolute(fee)

[pedromvpg]

You said you're using a port of BDK to typescript, which project is that?

@notmandatory it's happening on SatSigner. Here's where we're getting the issue: https://github.com/satsigner/satsigner/blob/7a928cd52d777568f6ee1a746ec7eb7be60ad3d9/apps/mobile/api/bdk.ts#L220