Skip to content

Conversation

@meeh0w
Copy link
Member

@meeh0w meeh0w commented Jan 7, 2026

Changes

  1. Attempts to recognize instances of user rejecting the transaction on the hardware wallet as opposed to the device failing to sign it.
  2. Fixes an issue where Ledger device must be connected and unlocked before onboarding/importing the wallet.

Testing

  1. Initiate any transaction (e.g. Send) and reject it on the device (Ledger or Keystone). You should NOT see the error toast.

    • Also do the same from Core Web, but in this case Core Web should not prompt you again after you declined it once.
  2. Go to Ledger import/onboarding with the device disconnected. You should be able to finish onboarding once you connect it (without the fix, you'd have to refresh the page)

Checklist for the author

  • I've covered new/modified business logic with Jest test cases.
  • I've tested the changes myself before sending it to code review and QA.

@meeh0w meeh0w merged commit 929813d into main Jan 7, 2026
5 checks passed
@meeh0w meeh0w deleted the fix/proper-rejection-statuses branch January 7, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants