We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When attempting to use MetaMask + Ledger to send a transaction with Ledger, the transaction immediately fails.
To Reproduce Switch MetaMask to Ledger Generate transaction Click to confirm transaction See notification that transaction failed
Expected behavior Transaction should transfer to Ledger User should be able to sign transaction with Ledger Transaction should be successful
Browser details (please complete the following information):
Additional context MetaMask error notification: Transaction failed! Error: TransportStatusError: Ledger device: Invalid data received (0x6a80)
The text was updated successfully, but these errors were encountered:
We are also seeing this. @BassBauman how did you resolve the issue?
Sorry, something went wrong.
@wjmelements this issue was resolved for me when I changed the Ethereum app settings on Ledger to the following:
Contract data -> YES Display data -> YES
Also see issue #43.
Thanks @BassBauman
No branches or pull requests
Describe the bug
When attempting to use MetaMask + Ledger to send a transaction with Ledger, the transaction immediately fails.
To Reproduce
Switch MetaMask to Ledger
Generate transaction
Click to confirm transaction
See notification that transaction failed
Expected behavior
Transaction should transfer to Ledger
User should be able to sign transaction with Ledger
Transaction should be successful
Browser details (please complete the following information):
Additional context
MetaMask error notification: Transaction failed! Error: TransportStatusError: Ledger device: Invalid data received (0x6a80)
The text was updated successfully, but these errors were encountered: