42 sats \ 9 replies \ @k00b OP 14 Feb \ parent \ on: SN release: NWC & LNBits for sending, LND for autowithdraw, NSFW labels, & more meta
Mind checking your console for errors and sharing which browser you're using?
Some browsers don't like some of the security settings we are asking it to enforce.
iOS 17.3.1 - Safari (PWA). Not sure if my string is good:
nostr+walletconnect://<long-alphanumeric-string>?relay=wss://relay.getalby.com/v1&secret=<secretstring>reply
reply
Going to add the validation tomorrow.
However, there should be a toast with some error message if the credentials are no good1:
The form also shouldn't close if the info event wasn't found. And if it was found, the wallet indicator should turn green.
But maybe the error is CSP + browser combination again which throws an error at a location which isn't toasted.
Footnotes
-
That check only verifies everything up to but not including the secret since a correct secret is not required to receive the info event unfortunately. ↩
reply
CSP?
reply
Oh, sorry, I mean Content Security Policy. This is supposed to tell your browser what code is good to run and which should get blocked. It might be blocking too much depending on the browser.