pull down to refresh
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.
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.
LNC is broken on master currently. It's not storing DH keys like you mentioned yesterday.
If you start from scratch, with it detached, not merely resaving an existing one, it fails for me.
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.
I think I fixed it. I'll push a pr in a second.
Never mind. It's still broken. Sometimes it works if I hard refresh after detaching for some reason.
Have you looked into your wallet logs? Anything useful in there?