Description:
If the user taps "back" when they have already scanned the QR code with keystone HW wallet, then goes forward again, they get a different QR Code. Signing fails because of this.
Steps:
- Use keystone hardware account
- Send amount to another user
- Scan QR code with keystone
- Tap back button to see the amounts / details on previous screen
- Forward again
- Scan keystone signature
Expected result:
Keystone signature is scanned, transaction is sent to chain
Actual result:
Signing fails, error message appears in UX
Regression:
This is because when we move from the info page to the QR page, we generate a new transaction - the transaction contains the same fields for amount, destination, etc, but has different fields for block height (?) ... so it creates a different QR code. Keystone signs the original QR code but the signature is different for a different QR code, so the signature will be invalid
For a fix we should probably show destination and amount on the QR code page, so users can compare to keystone display, and disable the back button.
Description:
If the user taps "back" when they have already scanned the QR code with keystone HW wallet, then goes forward again, they get a different QR Code. Signing fails because of this.
Steps:
Expected result:
Keystone signature is scanned, transaction is sent to chain
Actual result:
Signing fails, error message appears in UX
Regression:
This is because when we move from the info page to the QR page, we generate a new transaction - the transaction contains the same fields for amount, destination, etc, but has different fields for block height (?) ... so it creates a different QR code. Keystone signs the original QR code but the signature is different for a different QR code, so the signature will be invalid
For a fix we should probably show destination and amount on the QR code page, so users can compare to keystone display, and disable the back button.