synonymdev
[Bug]: Scanning a LN invoice QR fails without error
Describe the bug
If I use the camera scanner to scan a LN QR invoice, it immediately scans then goes back to the previous screen with no effect.
Reproduce
- Go to camera scanner from anywhere
- Scan a LN QR
- No effect after scanning, no ability to pay LN invoice
- No error message is given
Screenshots / Recording
No response
Operating system
iOS
Bitkit version
(23)
Log output
No response
Just tested this as well for a LN QR, cannot confirm this bug, scanner works on my side (23) (iPhone).
It could be the type of invoice being scanned. I tried paying at lnmarkets.com as a deposit -- try both the 0-amount invoice, and try generating a specific one.
Maybe there is something up with LNmarkets. 
LNmarkets also failed to generate a specific invoice.
Just tried again as the issues on LNmarkets side seem to be resolved. I am getting this error when scanning 0-amount invoice on LNmarkets. Bitkit does seem to be able to parse a specified invoice though (on LNmarkets). @coreyphillips @Jasonvdb @BitcoinErrorLog
When attempting to deposit to LNMarkets without specifying an amount, LNMarkets presents an lnurl-pay string via the qrcode. Unfortunately, Bitkit does not yet support lnurl at this time.
To successfully deposit to LNMarkets in the meantime, an amount must be specified in the textbox below the qrcode. Simply enter the desired amount of satoshis you wish to deposit and click "Request Invoice". This should generate an invoice that Bitkit can recognize.
I suppose then that the bug/feature here is to show appropriate error-handling/notification, and/or to add support for lnurl-pay.
@coreyphillips can I close the issue?
Please keep it open for now. A scanned lightning invoice containing capital letters followed by a colon (Ex: LIGHTNING:) will currently fail. I'll close this issue once that fix is in.
Working for the incoming build 39. If you select lightning invoice in WOS.
https://user-images.githubusercontent.com/5300488/232447162-03f42269-d1b3-4b01-b743-4b444dcbc5c6.MP4
ohhhh i think i see the issue, it defaults to Lightning Address... lame. I'm still not sure whether we should add support for that...
Right, yeah then I think every user is going to make that mistake if WOS is always going to default to lightning address
I never tried talking to them before, let's see... https://twitter.com/BitcoinErrorLog/status/1647901756137914368