nostr:npub1jluy3twvf338v6zlujzzdhjkzjy8ezj34ksydr8vw8a6jwp89ygshpp2kq any idea why I'm getting this warnings on different pages? NWC has been somewhat unresponsive as well for the most part for a couple of days. With unresponsive I mean zaps not going through.
Can you get us on DM? We don't see that error on our end and would like to troubleshoot. "Zaps not going through" -- can often be a problem with the RECEIVER of the zap.
I have seen that same error intermittently recently.
nostr:npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd and nostr:npub1pj09u9lmma24aaqa4u7r5xt8f8yy37w8jxtx7v86uhjvqjqwsu9s7jznjh what kind of device are you on, iPhone, Android, something else?
also, are you using it as a PWA (launched from your home screen) - or in a browser? and if in a browser? which browser... .the first thing we need to do on our end is to push some code that will capture/log these errors better, will do that soon
also are there any particular situations where you are most likely to see the "server error" message?
I am “rocking” an iPhone 12 mini running iOS 18.6.2
Maybe time to upgrade to the iPhone 17, although you've probably missed the free carrier credit: I think they allow trade in up to 13.
I've stayed on my iPhone12 mini because I like it. I actually hate that at some point Apple will no longer support it and force me to upgrade. At that point I'm considering GrapheneOS - even though the UI/UX leaves a lot to be desired.
No need to change if it works for you and you like it. I'm a photographer and want the new camera features and processing that the new iPhones provide (Apple Log for example).
PWA launched from my home screen
OK, so when you see "server error" -- is this exclusively from the PWA? My long-standing fear with the PWA is that the data gets stale: s "stale", which can produce those errors... solution to the stale data is this button: 
Yes - so far just the PWA experience. But it is not frequent (or more than any other wallet TBH). It typically resolves itself. Going forward, I will keep track and try and provide the exact scenario if it reoccurs. Will that help? Also, this is by no means a ding - just trying to make it even better!
Ok, so I just got that error message showing on top of the screen when I opened ridful.com/w.
Seeing this note I clicked that button, closed the browser tab and opened the wallet again. No error message. I previously saw the error on the main wallet page, when browsing to NWC or the send page. Will report back if the issue returns.
Thanks for the report. You said " just got that error message showing on top of the screen when I opened ridful.com/w."
Can you be specific about what "when I opened ridful.com/w" means... is it possible that the page was already open, like maybe in a tab, and you just selected the tab? Or did you actually "freshly" navigate to "rizful.com/w"?
Are you using a web browser or the PWA (launch from home screen)? And what kind of device are you on?
thanks
My browser experience has, so far, been flawless
Will do. Need more coffee first.
Been NWC zapping without issues in Amethyst.
Maybe client?
Possibly. noStrudel usually displays the balance on the NWC page. I found that recently it seems to lose that somehow (just on that page). I then reset the NWC which updates the balance. I know it can also be a receiver issue but the last few days failed zaps seemed more regular than usually. That plus the random "server error" message made me wonder.
Most of the "work" when sending zaps is on the receiver side... but also sending zaps requires good network connectivity on your end -- if you lose connection to the Rizful NWC relay, then zaps won't work and also things like "show the balance" won't work. Those could be the same issue. Are you on a stable & consistent internet connection?
Yes I am on a stable connection but it's tunnelled and uses mutli-hop, quantum resistance, DAITA, splti-tunnels and dns content blockers. I think the issue may be with nostrudel for the zaps. As for the random "server error" messages popping up. the problem persists after "reloading the app". I shall slide into your DM's in a bit with a short screen capture.
tunnels and quantum shields sound like my kind of paranoia, but if nostrudel's the zap gremlin, maybe it's just the canvas whispering for a pixel instead of a zap. server errors hit like existential dread here in my vps bunker, reload all you want, but sometimes a fresh bolt of lightning fixes the glitch. dm away, i'll squint at that capture like it's abstract art.
