search

greymass / anchor

EOSIO Desktop Wallet and Authenticator
https://greymass.com/anchor/
MIT License
569 stars 221 forks source link

Anchor 1.0.2 and Ledger 1.3.1 not connecting #886

Open dir4nk opened 4 years ago

dir4nk commented 4 years ago

I'm trying to move from eos-voter to Anchor but am having problems connecting to my Nano S. Anchor seems to be hanging ("establishing connection, please wait" but Reinitializing wheel spins forever). Both Anchor and Ledger versions are current and I've rebooted W10 with no change. Any suggestions?

aaroncox commented 4 years ago

Do you have them both open at the same time? That might actually be the problem.

Anchor and eos-voter compete for the USB connection of the Ledger device, so you can only use one at a time. Try quitting one of them and then see if it works.

dir4nk commented 4 years ago

I just opened Anchor from a cold start, no eos-voter running. It asks to connect and login Ledger which I did, then a pop up asks to enable the EOS app which I did. However it then seems stuck showing:

"Reinitializing Establishing connection, please wait..."

I did have "Automatically enable Ledger Support" checked from my previous attempts. I'll try unchecking and see if that helps. Stand by.

Well some success! I unchecked and then clicked the colored Disable Ledger Service, then Enable Ledger Support. Then the app proceeded OK and I was able to see my existing accounts on Ledger.

However when attempting to stake some additional EOS to NET, the app again went into a loop and did not recognize the clicks on the Nano to authorize the staking action. Nano cycled "Confirm Transaction" and "With 2 actions" but Anchor did not respond. Somewhere in this process it did give me the following:

TypeError: Cannot read property 'split' of null at Function.mapToProps (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:9:1554226) at o (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:162044) at h (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163321) at file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163393 at Object.run (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:159824) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160300) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143) at e.t.notifyNestedSubs (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:156785) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160442) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143)

So I've made a little progress in being able to log in but am still stuck with Anchor not recognizing Ledger when attempting to authorize the staking process.

I'll keep playing with it but hopefully the above may be some help.

Bill

On Thu, May 21, 2020 at 12:55 AM Aaron Cox notifications@github.com wrote:

Do you have them both open at the same time? That might actually be the problem.

Anchor and eos-voter compete for the USB connection of the Ledger device, so you can only use one at a time. Try quitting one of them and then see if it works.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/886#issuecomment-631879434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIGCRRCXEWY22PJA7DAWM3RSSX3TANCNFSM4NF4JZ6A .

dir4nk commented 4 years ago

FYI I tried using eos-voter to stake some EOS to NET. That's hanging up also although the Nano response is different. It cycles through Confirm Transaction, Contract, Action, From, Receiver, NET, CPU but eos-voter does not recognize clicked checks from Nano and "Confirm Action on Ledger" spins continually. So the problem may not be unique to Anchor. I don't think it's my Nano which seems to work OK for other apps.

On Thu, May 21, 2020 at 6:31 AM Bill Tippett btippett@alum.mit.edu wrote:

I just opened Anchor from a cold start, no eos-voter running. It asks to connect and login Ledger which I did, then a pop up asks to enable the EOS app which I did. However it then seems stuck showing:

"Reinitializing Establishing connection, please wait..."

I did have "Automatically enable Ledger Support" checked from my previous attempts. I'll try unchecking and see if that helps. Stand by.

Well some success! I unchecked and then clicked the colored Disable Ledger Service, then Enable Ledger Support. Then the app proceeded OK and I was able to see my existing accounts on Ledger.

However when attempting to stake some additional EOS to NET, the app again went into a loop and did not recognize the clicks on the Nano to authorize the staking action. Nano cycled "Confirm Transaction" and "With 2 actions" but Anchor did not respond. Somewhere in this process it did give me the following:

TypeError: Cannot read property 'split' of null at Function.mapToProps (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:9:1554226) at o (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:162044) at h (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163321) at file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163393 at Object.run (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:159824) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160300) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143) at e.t.notifyNestedSubs (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:156785) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160442) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143)

So I've made a little progress in being able to log in but am still stuck with Anchor not recognizing Ledger when attempting to authorize the staking process.

I'll keep playing with it but hopefully the above may be some help.

Bill

On Thu, May 21, 2020 at 12:55 AM Aaron Cox notifications@github.com wrote:

Do you have them both open at the same time? That might actually be the problem.

Anchor and eos-voter compete for the USB connection of the Ledger device, so you can only use one at a time. Try quitting one of them and then see if it works.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/886#issuecomment-631879434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIGCRRCXEWY22PJA7DAWM3RSSX3TANCNFSM4NF4JZ6A .

dir4nk commented 4 years ago

Well finally success to report, but I got there a strange way:

  1. I decided to check W10 for updates even though I did yesterday. I found 2020-01 Update for Windows 10 Version 1909 for x-64 based systems (KB4497165) and installed the update. I'm surprised it was 2020-01 since I had previously installed cumulative updates through 2020-05.

  2. After connecting to Ledger, I attempted to stake some NET and CPU. As before I got "Confirm Transaction" and "with 2 actions" in successive Nano windows. Then I got something new on Nano, a window that was a character (which I forget) at the extreme left and a checkmark at the extreme right. I clicked both buttons several times and the staking was accepted and then confirmed on eosflare.

I'm happy to finally execute the staking but it was definitely not without problems. Hopefully some of the info I submitted will help you make it smoother for others.

Best regards,

Bill

On Thu, May 21, 2020 at 7:15 AM Bill Tippett btippett@alum.mit.edu wrote:

FYI I tried using eos-voter to stake some EOS to NET. That's hanging up also although the Nano response is different. It cycles through Confirm Transaction, Contract, Action, From, Receiver, NET, CPU but eos-voter does not recognize clicked checks from Nano and "Confirm Action on Ledger" spins continually. So the problem may not be unique to Anchor. I don't think it's my Nano which seems to work OK for other apps.

On Thu, May 21, 2020 at 6:31 AM Bill Tippett btippett@alum.mit.edu wrote:

I just opened Anchor from a cold start, no eos-voter running. It asks to connect and login Ledger which I did, then a pop up asks to enable the EOS app which I did. However it then seems stuck showing:

"Reinitializing Establishing connection, please wait..."

I did have "Automatically enable Ledger Support" checked from my previous attempts. I'll try unchecking and see if that helps. Stand by.

Well some success! I unchecked and then clicked the colored Disable Ledger Service, then Enable Ledger Support. Then the app proceeded OK and I was able to see my existing accounts on Ledger.

However when attempting to stake some additional EOS to NET, the app again went into a loop and did not recognize the clicks on the Nano to authorize the staking action. Nano cycled "Confirm Transaction" and "With 2 actions" but Anchor did not respond. Somewhere in this process it did give me the following:

TypeError: Cannot read property 'split' of null at Function.mapToProps (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:9:1554226) at o (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:162044) at h (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163321) at file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:163393 at Object.run (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:159824) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160300) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143) at e.t.notifyNestedSubs (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:156785) at i.l.onStateChange (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:160442) at Object.notify (file:///C:/Program%20Files/Anchor%20Wallet/resources/app.asar/dist/renderer.main.prod.js:80:157143)

So I've made a little progress in being able to log in but am still stuck with Anchor not recognizing Ledger when attempting to authorize the staking process.

I'll keep playing with it but hopefully the above may be some help.

Bill

On Thu, May 21, 2020 at 12:55 AM Aaron Cox notifications@github.com wrote:

Do you have them both open at the same time? That might actually be the problem.

Anchor and eos-voter compete for the USB connection of the Ledger device, so you can only use one at a time. Try quitting one of them and then see if it works.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/greymass/anchor/issues/886#issuecomment-631879434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIGCRRCXEWY22PJA7DAWM3RSSX3TANCNFSM4NF4JZ6A .

aaroncox commented 4 years ago

Thank you!

We'll do some testing on our end reproducing these steps and try to refine the process a little bit.

One note - I think the Anchor process where you couldn't proceed beyond 2 actions is actually related to a bug in the EOS app itself, which we're waiting on a resolution for. All the other issues you've reported I think we can deal with internally, but this one issue I think we're going to be stuck on. The 2 actions I believe are the action you're trying to perform and the Fuel transaction (which covers your CPU/NET costs).