Skip to content

Commit

Permalink
Merge pull request #44 from obsidiansystems/191-troubleshooting
Browse files Browse the repository at this point in the history
Add fix for error 191 on macOS to troubleshooting in README
  • Loading branch information
matthewbauer authored Nov 6, 2019
2 parents 19fdf7a + b549039 commit 4587119
Showing 1 changed file with 36 additions and 0 deletions.
36 changes: 36 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -981,6 +981,42 @@ If the Ledger application crashes when you load it, there are two primary causes
* Out of date firmware: If the Ledger application doesn't work at all, make sure you are running firmware
version 1.5.5.

### Error "Unexpected sequence number (expected 0, got 191)" on macOS

If `tezos-client` on macOS intermittently fails with an error that looks like

```
client.signer.ledger: APDU level error: Unexpected sequence number (expected 0, got 191)
```

then your installation of `tezos-client` was built with an older version of HIDAPI that doesn't work well with macOS (see [#30](https://github.com/obsidiansystems/ledger-app-tezos/issues/30)).

To fix this you need to get the yet-unreleased fixes from the [HIDAPI library](https://github.com/signal11/hidapi) and rebuild `tezos-client`.

If you got HIDAPI from Homebrew, you can update to the `master` branch of HIDAPI like this:

```shell
$ brew install hidapi --HEAD
```

Then start a full rebuild of `tezos-client` with HIDAPI's `master` branch:

```shell
$ brew unlink hidapi # remove the current one
$ brew install autoconf autmake libtool # Just keep installing stuff until the following command succeeds:
$ brew install hidapi --HEAD
```

Finally, rebuild `ocaml-hidapi` with Tezos. In the `tezos` repository:

```shell
$ opam reinstall hidapi
$ make all build-test
$ ./tezos-client list connected ledgers # should now work consistently
```

Note that you may still see warnings similar to `Unexpected sequence number (expected 0, got 191)` even after this update. The reason is that there is a separate, more cosmetic, issue in `tezos-client` itself which has already been fixed but may not be in your branch yet (see the [merge request](https://gitlab.com/tezos/tezos/merge_requests/600)).

### Contact Us
You can email us at [email protected] and request to join our Slack.
We have several channels about baking and one specifically for our Ledger applications.
Expand Down

0 comments on commit 4587119

Please sign in to comment.