pull down to refresh

0 sats \ 8 replies \ @WeAreAllSatoshi 4 Aug \ parent \ on: Stacker Saloon
I didn’t follow all of this discussion. Do you think you’ve identified the issues for my specific case?
write
preview
50 sats \ 7 replies \ @ek 4 Aug
No, I was not :/
reply
201 sats \ 6 replies \ @WeAreAllSatoshi 4 Aug
Testing?
reply
150 sats \ 5 replies \ @ek 4 Aug
Oh, no, but we deployed Declarative Web Push. It should only affect iOS 18.4+ though 🤔
Was it only one notification?
/cc @sox
reply
150 sats \ 2 replies \ @ek 4 Aug
Could be that you got unlucky and we sent out a push notification with the new format while the old service worker was still running on your device
If that's the case, it shouldn't happen again
reply
100 sats \ 0 replies \ @WeAreAllSatoshi 4 Aug
I’ll keep an eye on it
reply
50 sats \ 0 replies \ @sox 4 Aug
That’s exactly it
reply
50 sats \ 0 replies \ @sox 4 Aug
Ah, damn I forgot that old service workers might still receive these new payloads that they can’t recognize.
Visiting SN will update the service worker, also the background updates will probably update it… I hope. I think I should’ve pushed this in two phases (maximum compatibility -> less bloat)
reply
100 sats \ 0 replies \ @WeAreAllSatoshi 4 Aug
Yes just one
reply