You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the WebLN wallet was enabled and we switch to anon, anon will also use the WebLN wallet because it only looks at wallet:webln (not scoped to user id).
However, if the WebLN prompt was canceled, we won't show a QR code because anon can't retry invoices.
This means that following attempts will simply do nothing and anon looks broken because WebLN prompts don't open again once they were canceled. Only a page reload brings back the WebLN prompt but still not possible to fallback to a QR code.
I think anons should be able to use WebLN but that we only try it if it was enabled while signed in is weird.
Screenshots
No response
Steps To Reproduce
Enable WebLN wallet
Switch to anon
Try to post something
Cancel WebLN prompt
Expected behavior
Anon can fallback to QR code if WebLN enabled or gets immediately shown a QR code
Logs
No response
Device information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the bug
If the WebLN wallet was enabled and we switch to anon, anon will also use the WebLN wallet because it only looks at
wallet:webln
(not scoped to user id).However, if the WebLN prompt was canceled, we won't show a QR code because anon can't retry invoices.
This means that following attempts will simply do nothing and anon looks broken because WebLN prompts don't open again once they were canceled. Only a page reload brings back the WebLN prompt but still not possible to fallback to a QR code.
I think anons should be able to use WebLN but that we only try it if it was enabled while signed in is weird.
Screenshots
No response
Steps To Reproduce
Expected behavior
Anon can fallback to QR code if WebLN enabled or gets immediately shown a QR code
Logs
No response
Device information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: