unchained-capital / caravan

Bitcoin multisig coordination software
https://unchained-capital.github.io/caravan/
MIT License
203 stars 177 forks source link

Invalid Channel Error - Unable to Maintain Connection to Bitcoin App during Import Process #186

Closed JeremyNau closed 3 years ago

JeremyNau commented 3 years ago

I'm submitting a…

Expected Behavior

When creating a multi-sig wallet, and using a Ledger Nano X device, I should be able to import my xPub after I log into my device, access the Bitcoin App, and press the "Import Extended Key" button.

Current Behavior

I am unable to import my Xpub from my Ledger. As soon as I press the Import Public Key Button, I am prompted to connect to my device. Upon doing so, I am automatically disconnected from the bitcoin app on my Ledger and my key is not imported.

It seems doesn't occur 100% of the time for some reason, but has happened about 2/3 of the time for me.

It also seems to only occur when I am trying to create a Wallet. I have no issues when creating an address.

image

Steps to Reproduce (for bugs)

image

image

Environment

Using a Windows Device Tried on both the Brave and Windows browsers Tried using both Nano Ledger X and S

Please fill out the following:

JeremyNau commented 3 years ago

I have been running a few tests and getting errors. Any thoughts on what could be driving these errors?

image

image image

JeremyNau commented 3 years ago

Same resolution as closed #182

waldenraines commented 3 years ago

I have been running a few tests and getting errors. Any thoughts on what could be driving these errors?

@JeremyNau did you set up your wallet with the words from the initial page of the test suite?

gscreenshot_2020-12-14-083015

waldenraines commented 3 years ago

See also https://github.com/unchained-capital/caravan/issues/187

JeremyNau commented 3 years ago

No I did not. I'll have to test it and look out for that.

waldenraines commented 3 years ago

No I did not. I'll have to test it and look out for that.

Yeah, the test suite tests utilize a 2/2 multisignature with one of the two on the public words displayed in the test suite. The other set of private keys are held by the developers.

It's meant to test the actual devices and their software against some common usecases and thus requires the device under test to be set up on the words displayed in the test suite.