Closed jim618 closed 8 years ago
If you try this with a Trezor (change PIN, sign) when you do the sign you get a 'there is a new device, do you want to use it?' alert and then a PIN and encrypt challenge. You can then do a sign.
It is a bit round-the-houses but the app doesn't crash and once you've entered the PIN you can sign.
Yes, this all part of the more specialised event handling required for additional wallet modes.
It turns out that there is a subtle difference in the response from a "resetToAttached" between a Trezor and KeepKey. The Trezor reattaches, whereas the KeepKey doesn't (at least in firmware 1.0.0). Using a "resetToConnected" which is arguably more appropriate in this use case fixes the issue so I'm not going to pursue it.
Also I uncovered a few places in the wizard report screens where a hardware failed was unbranded. These are now fixed.
Ready for review and close.
KeepKey: This all works smoothly now. After a change PIN, when you sign a message your are asked if you want to sign a message on the KeepKey, then asked for your PIN, then returned to the Sign Message screen. Smooth.
Trezor: Workflow is the same as with KeepKey.
Closing
If you change the PIN value and then do a sign message, the PIN matrix is shown (on a KeepKey) but it crashes MBHD with: