pull down to refresh
I didn’t follow all of this discussion. Do you think you’ve identified the issues for my specific case?
No, I was not :/
Testing?
Oh, no, but we deployed Declarative Web Push. It should only affect iOS 18.4+ though 🤔
Was it only one notification?
/cc @sox
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
I’ll keep an eye on it
That’s exactly it
Yes just one
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)
Can you reproduce what you meant? I think I got confused by what I saw. I thought I saw me not being subscribed to ~security, but not sure if I really wasn't subscribed or not.
The button seems to reflect the state correctly:
also still correct after page reload
The action is correctly represented, it's client-side navigation that breaks the state
ohhh, I see
Subscribing to a territory won't change the status on the territory header until the next full refresh
I actually thought something different was happening, but when I tried again I discovered this different little behavior
lol wrong vid sorry, fixed
Wait!
Subscribing to a territory won't change the status on the territory header until the next full refresh
But you are indeed subscribed: