That is so strange. But it's a bug and will hunt it down.
Do you have any other Nostr accounts logged into Amethyst in this phone?
Or if you want to create a new account with the same lnaddress to receive, I can zap your new account to see if the notification shows up. In that way we know if it is an app/phone issue or if it is an account issue.
Yes, I just tested another profile nostr:npub1cd32tje2tyhcnm3mwen2hwcghs0vfyupcxjd9aff9e64rhgu755qa9wt08 with the same LN address and it shows the zaps on the notifications...WTF is wrong with my profile?? :-/
I suspect one of my past zaps has some data which causes an exception in the code which leads to all zaps being ignored. I'll try to debug it since it might be extremely difficult for you to reproduce it.
Ok finally I found out what was wrong. I'm using nostdress connected to my LND node to generate the invoices and publish the zap receipts (9735). And I was using my own private key to sign the receipts. I didn't pay attention to nostdress config doc which said to not use your own. I quickly checked nip-57 and didn't see anywhere mention to not use your own privKey to sign the receipt. Since Amethyst's NotificationFeedFilter has a filter condition to exclude events which author is the loggedInUser it explains the behaviour I was getting. After changing to a new generated privKey to sign the receipts everythingd seems to be working. Do you know the reason it shouldn't use its own privKey to sign the receipt?
Ohhh that makes sense. I can fix that user check.
You should probably not use your main key for security reasons. They might not have everything in place to keep it safe.
It's self-hosted nostdress, so I didn't think would be a problem. Are you aware of any other reason you shouldn't sign your own zap receipts??
