pull down to refresh

88 sats \ 11 replies \ @ek 24 Aug \ on: 3 Hours Not Using SN Wallet: My Impressions meta
Still, I have had a few failed zaps. I can't determine as of yet why some succeed and others fail.
Have you looked into your wallet logs? Anything useful in there?
write
preview
186 sats \ 10 replies \ @siggy47 OP 24 Aug
I just carefully looked. I am very happy to say that NOT ONE of my NWC zaps failed. All of the failures were with LNC. I think what happened was I noticed some more failed LNC zaps after I switched to NWC. I was mistaken. BTW, that wallet log is great. I should have checked it before posting. I didn't notice it before. I am keeping this setup. I should know soon enough if any more of my zaps fail. So far, so good.
reply
119 sats \ 9 replies \ @ek 24 Aug
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.
reply
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.
view replies