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
QR code scanner fails on quorum scan of xpub #6105
Comments
thank you for the report! can you pls provide all the qr codes that you are trying to import? and the whole wallet setup. |
I'm creating a new 2 of 2 quorum. These are dummy seeds. Anything else you need? Are you able to reproduce? |
I have the same problem in 6.5.5. I had to downgrade to 6.4.8 and it works fine. I've not tested any other versions other than these two. |
I am using 6.5.5 as well. I'm also trying to create a 2 of 3 Multisig vault. I'm trying to import the key vs scanning with a QR code. When I select import file, select the key generated from the other wallet, BlueWallet just brings me back to the camera looking to scan a QR code. I've replicated the on the MacOS desktop running BW 6.5.5 as well as other iOS devices running 17.3.1 Thanks |
@pointbiz thanks that was very helpful! was able to reproduce and submitted a fix |
Are you reporting a bug?
Please provide:
Android Samsung S22
6.5.1
Yes
Setup a 2-of-2 vault quorum.
Key 1 import 12-word phrase
Key 2 import xpub via scanner (or static image) by sharing on a secondary phone that you inputted the Key 2 12-word mnemonic. The scanning fails.
The QR code with "ur:crypto-account" doesn't scan, the camera just stays open trying to scan.
If you open this QR code as an image then it loads a black screen with a loading indicator and it's stuck in a loop.
If I try to paste the "ur:crypto-account" in the import box it says invalid mnemonic. If I paste the xpub in wallet descriptor format like shown below it says invalid.
[Abcdabcd/48'/0'/0'/2']Zpub6525
I expect it to be smart enough to accept this wallet descriptor format.
If I paste just the Zpub in the import box then it recognizes it and prompts me for the fingerprint then prompts me for the derivation path.
Please investigate.
The text was updated successfully, but these errors were encountered: