Skip to content
New issue

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

Empty error when attempting to sign using the updated ledger firmware #100

Closed
evan-forbes opened this issue Oct 10, 2023 · 2 comments
Closed

Comments

@evan-forbes
Copy link

Previous to the 2.2.2 ledger nano X firmware upgrade, we were able to sign transactions via the cli. Now, after updating to 2.2.2, the ledger is unable to sign and nothing happens. please see celestiaorg/celestia-app#2650 for more details.

From that issue:

Summary of Bug

When attempting to sign any TX with ledger hardware wallet an empty error is thrown with a second delay.

celestia-appd tx sign tx-test.json --from ledger-test --chain-id="mocha-4" --offline -s 0 -a 0 --ledger
Default sign-mode 'direct' not supported by Ledger, using sign-mode 'amino-json'.
Error:
I tried playing around with various options and flags - the result is always the same

@keyleu
Copy link

keyleu commented Oct 20, 2023

Hello, we are having the same issue on our chain (Coreum) with CLI.

Actually the issue for me is not with the firmware update but with the app version. The previous ledger-cosmos app version (2.34.9) in the marketplace worked without issues with CLI. In fact, if I take that version from the repository and compile it and install it using the ledger extension on my device with the new firmware, it still works.

The problem comes when I take the app version 2.34.12 (or any superior version that is not released yet, 2.35.*), the CLI is not compatible anymore. We get the same error as described above. After attempting to sign a message, it will throw an empty error without any description.

@evan-forbes
Copy link
Author

hey @keyleu this only works for apps built in go afaiu, but we just used a version of the sdk that bump this dep to v0.13.1 and the issue was resolved for us. I actually forgot to close this!

please feel free to reopen @keyleu if this is still an issue for you

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

No branches or pull requests

2 participants