Zaps fake confirmed & connections don't properly delete (NWC in Umbrel)

[Freakoverse]

Installed the NWC in my Umbrel node, and I made a connection with Amethyst, though I don't have an LN channel set up, and yet I can still "Zap". It was also "confirmed" in the NWC app as shown in the "current usage", and in Ameythst as indicated by the increased number and highlighted zap icon (Amethyst dev notified), but nothing was actually sent of course. (Expected an error or something but it "went through".

The other issue:

If I disconnect a connection and create a new one, it saves the previous permissions and historical spending in current usage. It doesn't actually make a fresh connection aside from changing the app connection pubkey.

This would also apply to a second connection, a new second would have the old seconds permissions.

I'm assuming this follows for 3rd, 4th, etc.

[bumi]

Thanks for reporting.
That's a good point. The "last accessed" date currently does not check if it was successful or not. There have also been thoughts on showing a complete audit log that users can see every action and the outcome - What do you think about that?
And should last-accessed be the last access that lead to a payment?

It also seems that the clients often do not propagate the error to the user in the apps. Some implement it as fire-and-forget.

[kiwiidb]

Hey @Freakoverse I've made a PR to fix the issue with deleting permissions, good catch.
However, I could not reproduce the zapping issue on Amethyst. Are you sure the zap didn't just go through?

[Freakoverse]

Hey @Freakoverse I've made a PR to fix the issue with deleting permissions, good catch. However, I could not reproduce the zapping issue on Amethyst. Are you sure the zap didn't just go through?

Thanks!
I'm assuming the zapping issue with Amethyst is on Amethyst's side and has been fixed potentially. Here's the convo:
https://snort.social/e/note1euc4lms2dxay0av8vuzcd60aytsgpmlyh82cfcl7wh2420ccxexq0tnqhj