`unexpected interaction request: Button` when creating a contract with `--trezor`

[mpeyfuss]

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

1.5.1-stable

What version of Foundryup are you on?

1.6.1

What command(s) is the bug in?

forge create / forge script

Operating System

macOS (Apple Silicon)

Describe the bug

When using Foundry with the --trezor flag to deploy a contract, run a script, or send a transaction request, I get an error message on the CLI of unexpected interaction request: Button.

This causes the transaction confirmation to reset on the trezor. I can't actually get through to signing the transaction because it keeps resetting.

I don't get this issue when sending transactions through Rabby on the browser.

Steps to reproduce the behavior:

• Clone the foundry starter repo to deploy the Counter contract on Sepolia testnet.
• Run forge create src/Counter.sol:Counter --rpc-url https://ethereum-sepolia-rpc.publicnode.com --trezor --broadcast
• Try to sign the transaction
• See error

I've submitted a report to trezor here, but wondering if anyone else can replicate.

[mablr]

I don't have a Trezor wallet to confirm, but given the error message unexpected interaction request: Button, it seems that the error is raised on trezor firmware side.

maybe @figtracer ?

[figtracer]

I don't have a Trezor wallet to confirm, but given the error message unexpected interaction request: Button, it seems that the error is raised on trezor firmware side.

maybe @figtracer ?

i can try this out in a bit

[mpeyfuss]

Thanks @mablr @figtracer! Yeah I lean towards it being an issue on the firmware, but also feel like I'm going crazy 😂

FWIW, Trezor Suite won't allow contract deployments through remix still because to is undefined for contract creations so a firmware issue wouldn't surprise me too much.

[figtracer]

i can't reproduce this in 1.5.1-stable nor the latest main on my safe 3 so this is likely an issue with the safe 5 (?) @mpeyfuss

[felipecsl]

I'm seeing the same issue with Trezor Safe 5 and forge 1.5.1-stable

[mpeyfuss]

Thanks @figtracer - I'll follow up on the trezor firmware side. Were you on the latest trezor firmware?

[figtracer]

yes