Hardware wallet not detected at swap confirmation

If the hardware device is not detected, stop at the connection layer. A missing signing prompt is not a reason to type the device’s recovery phrase into the browser or swap application.

Check the supported connection path

Use the wallet and hardware vendor’s current instructions for your exact device, browser and operating system. Confirm the device is unlocked, the required chain application is open and the chosen cable or connection method supports the integration.

MetaMask’s hardware-wallet guide explains that connected hardware accounts still require the device to sign. It also lists device, browser and application compatibility checks. Interface and transport support change, so avoid applying an old workaround blindly.

Separate detection from transaction review

A device can be detected but refuse a signing method or unsupported transaction. Read its message and the wallet’s detailed error. Enabling blind signing merely because a transaction is inconvenient is not equivalent to solving a connection problem.

Close competing applications only where the vendor’s guidance recommends it. Reconnect through the official hardware-account flow and compare the account address; a different derivation path can show another account without implying funds moved.

After reconnecting, refresh the quote and confirm there was no earlier signed submission. The device may have signed successfully while the browser failed to display the result.

If support is needed, provide device model, firmware/application versions, connection method and error text. Your private keys and recovery phrase are unnecessary for diagnosing device discovery.