pull down to refresh

0 sats \ 7 replies \ @ek 15 Feb freebie \ parent \ on: SN release: top territories, linked accounts in profile, deeper bolt11 deletion meta
:(
My NWC shows a red light
Can you unattach and retry if you didn't already? It should validate the connection string in more detail now. It also shouldn't close the form if no connection to the wallet was possible--but seems like it might do anyway for some reason. Which browser are you on?
We might need to add some opt-in client-side logging1 to find out what is going wrong for some stackers.

Footnotes

  1. It already exists but only logs push notification issues. ↩
write
preview
0 sats \ 6 replies \ @BitByBit21 15 Feb
I've tried with Brave, Firefox and Chrome but I still get the same red light.
reply
209 sats \ 1 reply \ @ek 16 Feb
What's confusing is that it works for me on Brave, Firefox and Chrome.
What operating system and which browser version are you running?
reply
0 sats \ 0 replies \ @BitByBit21 16 Feb
  • MacOS 14.2.1: Safari 17.2.1, Brave v 1.62.165, Chrome 121.0.6167.184
  • Windows 11 64 bits: Brave v 1.62.165, Firefox v 122.0.1, Chrome 121.0.6167.162
  • Android 10: Brave Nightly 1.64.72, Firefox 122.1.0
  • Mullvad VPN, but still get issues when it is disabled.
reply
0 sats \ 3 replies \ @k00b OP 15 Feb
Do you get anything in the browser console?
reply
1918 sats \ 2 replies \ @BitByBit21 15 Feb
Uncaught (in promise) CompileError: WebAssembly.compile(): at o.fromBase64 (content-script.js:2:2534119) at content-script.js:2:2534319 at I.a (content-script.js:2:2857805) at 39718 (content-script.js:2:2533793) at I (content-script.js:2:2857284) at content-script.js:2:2836069 at I.a (content-script.js:2:2857805) at 4690 (content-script.js:2:2835546) at I (content-script.js:2:2857284) at content-script.js:2:2505330
reply
21 sats \ 1 reply \ @k00b OP 15 Feb
Aha it is a wasm thing! Thanks!
reply
0 sats \ 0 replies \ @BitByBit21 15 Feb
Thank you for your support! Keep up the good work! :-)
reply