What happened?
With a passphrase (hidden) hardware wallet and the Trezor fully powered off, starting a transfer that prompts for passphrase then fails with a wrong / unknown / generic error toast instead of the blue Connect Device reconnect toast.
Logs (export bitkit_logs_2026-09-11_10-29-37):
=== Opening passphraseHost session for ble:…; hadSession=false ===
Wallet mode set to passphraseHost
App Error [BitkitCore.TrezorError.DeviceNotFound]
Send from the same passphrase wallet with device off was OK in this session (no bad toast); transfer is the failing path.
Expected behavior
Map TrezorError.DeviceNotFound (and equivalent connect failures during passphraseHost reopen) to the Connect Device toast (“Could not connect to your hardware device…”), not a generic/unknown error.
Steps to Reproduce
- Pair a Trezor with a passphrase (hidden) wallet; leave that wallet selected.
- Power the Trezor fully off.
- Start a Transfer that requires HW passphrase (e.g. involving the passphrase wallet).
- Enter passphrase when prompted.
- Observe wrong/unknown/generic toast instead of Connect Device.
Logs / Screenshots / Recordings
Actual toast (transfer / Sign With Device, Trezor off):
Expected toast (reference — Connect Device):
Logs:
2026-09-11-passphrase-offline-unknown-error-logs.zip
=== Opening passphraseHost session for ble:…; hadSession=false ===
Wallet mode set to passphraseHost
App Error [BitkitCore.TrezorError.DeviceNotFound]
Bitkit Version
TBD
Device / OS
TBD
Reproducibility
Always (transfer with device off + passphrase prompt)
Additional context
What happened?
With a passphrase (hidden) hardware wallet and the Trezor fully powered off, starting a transfer that prompts for passphrase then fails with a wrong / unknown / generic error toast instead of the blue Connect Device reconnect toast.
Logs (export
bitkit_logs_2026-09-11_10-29-37):Send from the same passphrase wallet with device off was OK in this session (no bad toast); transfer is the failing path.
Expected behavior
Map
TrezorError.DeviceNotFound(and equivalent connect failures during passphraseHost reopen) to the Connect Device toast (“Could not connect to your hardware device…”), not a generic/unknown error.Steps to Reproduce
Logs / Screenshots / Recordings
Actual toast (transfer / Sign With Device, Trezor off):
Expected toast (reference — Connect Device):
Logs:
2026-09-11-passphrase-offline-unknown-error-logs.zip
Bitkit Version
TBD
Device / OS
TBD
Reproducibility
Always (transfer with device off + passphrase prompt)
Additional context
DeviceNotFoundduring passphraseHost open is not mapped to.reconnect/ Connect Device; transfer path surfaces.generic.AppError).