Ledger-live-desktop: Unable to Sync ERC-20 tokens with latest update

[incomingstick]

Ledger Live Version and Operating System

• tested on Ledger Live 1.14.0 (Desktop)

• Platform and version: Arch - Linux Kernel 5.2.11

• tested on Ledger Live 1.4.0 (3145768) (Mobile)

• Platform and version: Android - Mobile Linux Kernel 4.4.153-15480

• Ledger Nano X Ethereum App version 1.2.7

• Ledger Nano X Bitcoin App version 1.3.13

Expected behavior

Ledger Live has prompted me to run a "Ledger Live Account Update" on my Ethereum addresses. I would expect it to sync my ERC-20 tokens.

Actual behavior

The update does not complete. On the desktop version I get an error that reads:

Dynamic Exception type std::invalid_argument
std::exception::what: invalid hex character.
Something went wrong.  Please retry or contact us.

On mobile it does not give a detailed error, it just says:

Something went wrong with the blockchains synchronization. Please retry or contact us.

Steps to reproduce the behavior

Run the ERC-20 Ethereum update.

[gre]

Thanks for the report, we've never yet experienced this error, seems to be new and related to the recent Ethereum iteration.

Would you mind contact our ledger tech support to provide exported logs?

alternatively, if you are dev and want to dig on your end, you can try to use VERBOSE=1 ledger-live sync (on CLI, https://www.npmjs.com/package/ledger-live ) and see if you get an error at the end too.

The error so far is not precise enough for us to understand the problem but I hope we can identify it as soon as possible. Thanks

[incomingstick]

Thank you for responding quickly! I will look to do both as soon as I can and reply here once I have more info for you.

Edit: As a side note, it also looks like the core-js version used by the 'ledger-live' npm package is out of date. npm warns: npm WARN deprecated [email protected]: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.

[incomingstick]

I have submitted the logs exported from Ledger Live.

I am interested in testing the command you mentioned, VERBOSE=1 ledger-live sync, however I am having trouble installing it. When I run npm i -g ledger-live I receive the following node-pre-gyp warning:

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://github.com/sandeepmistry/node-bluetooth-hci-socket/releases/download/0.5.3-1/binding-0.5.3-1-node-v72-linux-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for @abandonware/[email protected] and [email protected] (node-v72 ABI, glibc) (falling back to source compile with node-gyp)

It then attempts to source compile, as it says it will, and that compilation fails with a plethora of errors. ledger-live does install, but when executed it fails as the @abandonware/bluetooth-hci-socket dependency never gets installed.

I looked into the the 404 error that node-pre-gyp gives. It is just a simple case of a user rename, and following the link (https://github.com/sandeepmistry/node-bluetooth-hci-socket) actually directs you here (https://github.com/noble/node-bluetooth-hci-socket).

The ledger-live install failure is clearly an upstream issue, but it is something you probably should be made aware of, if you are not already. I do wonder if you have any suggestions on how I could supersede this dependency issue? I will admit, I am not as familiar with npm as I should be.

[gre]

Thanks.

ok sorry for the ledger-live troubles, we'll investigate why ledger-live does not work and what can be done. @meriadec do you think you can take a bit of a look when you have some time? ArchLinux + live-common's tool. I know since the (Proof of concept of NanoX support) bluetooth lib addition it created some issues, we actually have disabled it on Windows, sad if we couldn't make it work.

[luismasserral]

I'm having the same problem here:

Device: Ledger Nano S
Software: Ledger Live 1.14.0
SO: Ubuntu 19.04

[TheRealBluesun]

UPDATE: v1.15.0 still has this issue
I'm having the same issue.
Device: Ledger Nano S (Secure Element v1.5.5, MCU v1.7)
Software: Ledger Live 1.14.0, 1.15.0
OS: Linux Mint 19.1 Cinnamon 4.0.10

[dbastianello]

Same problem here

[incomingstick]

@gre @meriadec I tried installing ledger-live via npm again tonight and it worked. I then tried running VERBOSE=1 ledger-live sync while my Ledger Nano X was connected to the computer, logged in, and in the Ethereum App. I had the GUI Ledger Live open next to it to confirm that it was connected, so I hope that doesn't make a difference. Though, given the output it doesn't seem it should. Running VERBOSE=1 ledger-live sync in this state returned the following output:

debug: apdu: => b001000000
debug: hid-frame: => 8ee30500000005b00100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
debug: hid-frame: <= 8ee305000000120108457468657265756d05312e322e379000000000000000000000000000000000000000000000000000000000000000000000000000000000
debug: apdu: <= 0108457468657265756d05312e322e379000
(node:15544) UnhandledPromiseRejectionWarning: Error: Could not locate the bindings file. Tried:
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/build/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/build/Debug/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/build/Release/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/out/Debug/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/Debug/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/out/Release/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/Release/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/build/default/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/compiled/12.10.0/linux/x64/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/addon-build/release/install-root/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/addon-build/debug/install-root/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/addon-build/default/install-root/ledger-core-node.node
 → /home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/lib/binding/node-v72-linux-x64/ledger-core-node.node
    at bindings (/home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/bindings/bindings.js:126:9)
    at Object.<anonymous> (/home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/ledger-core/js/index.js:1:55)
    at Module._compile (internal/modules/cjs/loader.js:936:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
    at Module.load (internal/modules/cjs/loader.js:790:32)
    at Function.Module._load (internal/modules/cjs/loader.js:703:12)
    at Module.require (internal/modules/cjs/loader.js:830:19)
    at require (internal/modules/cjs/helpers.js:68:18)
    at Object.lib (/home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/lib/live-common-setup.js:94:14)
    at lazyLoad (/home/user/.nvm/versions/node/v12.10.0/lib/node_modules/ledger-live/node_modules/@ledgerhq/live-common/lib/libcore/platforms/nodejs.js:53:17)
(node:15544) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:15544) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It seems it is unable to locate ledger-core-node.node in the package. Running ledger-live does produce the common help menu and the logo, but I am not able to run ledger-live verbose as it crashes with similar but slightly lengthier output. I can provide it here if you would like, but it is essentially the same error.

I do not believe this to be related to my initial issue, and it appears to be an issue with the npm package.

On a more relevant note, my initial issue does still seem to be reproducible with the latest GUI update.

[LevinGermann]

I see this problem as well, similar setup...

{
    "level": "error",
    "message": "Dynamic exception type: std::invalid_argument\nstd::exception::what: Invalid hex character\n",
    "pname": "renderer",
    "stack": "Error: Dynamic exception type: std::invalid_argument\nstd::exception::what: Invalid hex character\n\n    at deserializeError (/opt/ledger-live-desktop/resources/app.asar/node_modules/@ledgerhq/errors/lib/helpers.js:76:15)\n    at EventEmitter.c (file:///opt/ledger-live-desktop/resources/app.asar/webpack:/src/helpers/ipc.js:65:25)\n    at emitTwo (events.js:130:20)\n    at EventEmitter.emit (events.js:213:7)",
    "timestamp": "2019-09-29T18:28:51.179Z"
}

[gre]

Fix has been identified and is going to be delivered in next version of Ledger Live. ETA ~1 month.

[dbastianello]

Thank you for the update.

On Wed, Oct 2, 2019, 12:12 PM Gaëtan Renaudeau [e-mail]
wrote:

Fix has been identified and is going to be delivered in next version of
Ledger Live. ETA ~1 month.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LedgerHQ/ledger-live-desktop/issues/2327?email_source=notifications&email_token=ACSES75HWH2XZSQGGOSXSVTQMTCAVA5CNFSM4IUUNB6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAFJ7MI#issuecomment-537567153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSES74CTYTZSPPTO4A4FWDQMTCAVANCNFSM4IUUNB6A
.