CLI panics when formatting output after successful contract invocation when return type is BytesN<32>

[mugane-dj]

stellar version

stellar 25.2.0 (2848488)
stellar-xdr 25.0.0 (dc9f40fcb83c3054341f70b65a2222073369b37b)
xdr curr (0a621ec7811db000a60efae5b35f78dee3aa2533)

What did you do?

Invoked a schedule operation

stellar contract invoke \
    --id $TIMELOCK_ID \
    --source deployer \
    --network-passphrase "$NETWORK" \
    -- \
    schedule_op \
    --target $TIMELOCK_ID \
    --function upgrade \
    --args "[{\"bytes\":\"055ef816223ee5216b18c2df00d615ee089a8ef11b927a764e4f5d6c0cb4f4c7\"}]" \
    --predecessor 0000000000000000000000000000000000000000000000000000000000000000 \
    --salt 10561faae77b148a71ecd7f4bb22b653975b46e1430e19280e62978acaa39814 \
    --delay 600 \
    --proposer $DEPLOYER

What did you expect to see?

Operation ID to be output by the CLI

What did you see instead?

ℹ️ Simulating transaction…
ℹ️ Signing transaction: fa3bb43c15c2da1d721cc1eeb6ae3f4b378120d3119828568d6e3bbd19dae72b
🌎 Sending transaction…
✅ Transaction submitted successfully!
🔗 https://stellar.expert/explorer/testnet/tx/fa3bb43c15c2da1d721cc1eeb6ae3f4b378120d3119828568d6e3bbd19dae72b

thread 'main' (185501) panicked at cmd/crates/soroban-spec-tools/src/lib.rs:593:27:
not yet implemented: Bytes(
    ScBytes(
        BytesM(055ef816223ee5216b18c2df00d615ee089a8ef11b927a764e4f5d6c0cb4f4c7),
    ),
) doesn't have a matching Val
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace