I wanted to send you a serious tip for this since it really helped me a lot.
I thought, "hmm.. what would be a good amount to send? I wonder how many sats $4.2069 would be?", so did the math: (BTC price was 67644 when I did this)
Discussion
I checked my sats balance in my Alby firefox extension. It was too low for what I wanted to send, so I added 7000 more sats to my Alby wallet from another wallet.
Once I had enough sats in my Alby wallet, I clicked the [Z] (zap) button on your note. This was in coracle, using Firefox+Alby.
When I clicked the [Confirm Payment] button, the spinner just kept spinning for a long time. I waited a few minutes. Eventually it error'ed out with "No preimage in result":
I checked my Alby wallet balance.
The 6219 sats were gone.
No sign of where they went.
There is nothing showing in the Alby firefox extension history, or in the transaction log on getalby.com, so it's as if the sats just disappeared.
I waited a couple hours hoping they would magically reappear. Nope.
Please check to see if you received them.
Until the whereabouts of those missing sats is figured out, I am not using Alby anymore to send more zaps.
This screenshot of my alby balance shows that the current balance does not make sense. I added +7000 sats to increase my balance before sending the 6219 to you. There is no way the balance could be 3860 when my last transaction in there shows +7000.
Either you did receive the 6219 sats successfully and alby missed it somehow, or alby owes me those 6219 sats.
I've seen the "No preimage in result" error a few other times I've zapped small amounts but I didn't think much of it so didn't care about tracking the exact sats balance or try to figure out what happened. Now with $4.2069 worth of sats, I am determined to figure out what is happening when the "No preimage in result" error appears.
Glad I could help. I got your zap. I use zeuspay. It has a zaplocker, which means I have to open the app to redeem. (I opened it just now)
Thank you for the zap 🤙🏾
Hey, it seems that your 6219 zaps were sent correctly to nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve!
Sometimes the receiving lnurl server fails to issue the receipt, and clients are not notified immediately. That's how it works now, every month such issues are becoming more rare. But sats are never gone, they either return to sender or appear at the receiving side after short time.
Happy to see you troubleshooting!