pull down to refresh

119 sats \ 9 replies \ @ek 24 Aug \ parent \ on: 3 Hours Not Using SN Wallet: My Impressions meta
Yeah, the notification that a zap failed can be delayed. We only know that it definitely failed when the invoice expires. I guess that was why you received some "zap failed" notifications even after you switched to NWC.
write
preview
0 sats \ 8 replies \ @k00b 24 Aug
LNC is broken on master currently. It's not storing DH keys like you mentioned yesterday.
reply
0 sats \ 7 replies \ @ek 24 Aug
Huh, weird, I tested it yesterday and I saw them getting saved thanks to fa881a1a which is included on master in 789d7626.
reply
0 sats \ 6 replies \ @k00b 24 Aug
If you start from scratch, with it detached, not merely resaving an existing one, it fails for me.
reply
0 sats \ 5 replies \ @ek 24 Aug
Mhh, I could swear it worked for me yesterday and at my first attempt today but when I started recording to prove, it's indeed not saving them even though we return the credentials in testSendPayment.
But I found another bug, PR incoming after confirmation.
reply
0 sats \ 4 replies \ @k00b 24 Aug
I think I fixed it. I'll push a pr in a second.
reply
0 sats \ 3 replies \ @k00b 24 Aug
Never mind. It's still broken. Sometimes it works if I hard refresh after detaching for some reason.
reply
0 sats \ 2 replies \ @ek 24 Aug
Seems to work consistently for me after hard refresh, see this video. This must have been what I've seen yesterday and initially today.
My guess would be that detach doesn't completely reset LNC.
reply
0 sats \ 1 reply \ @k00b 24 Aug
It's disconnecting according to lnc-web's api. I suspect lnc-web is holding onto to some state that it shouldn't be.
view replies