Windows Push Notification Service - 'ttl' support appears broken
I've successfully got VAPID cert based Push Notifications working (Chrome, FireFox, Edge on Windows and Android)
ttl header value when sending a push notification to the
sg2p.notify.windows.com endpoint (Edge for Windows subscription) is having no effect.
It seems that the Push Notification is being handled like the old
toast notifications, i.e. if the device is not online then the notification is always discarded regardless of any
ttl setting (in the old case it was
So the end result is I can send Push Notifications with
ttl values for up 4 weeks in the future for any subscription that hits either the Google FCM or Mozilla endpoints, and it will get delivered as soon as that browser is started. But not Edge on Windows where the effective
ttl is 0.
Apologies for what is probably the wrong 'tag' - I can't find any tag for
Windows Notification Services
Do you mean the Windows Push Notification doesn't work in Edge on Windows? Which version of Edge and Windows OS are you using?
Could you please provide a minimal code sample which can reproduce the issue, so that we can have a test?
You can also refer to this blog for more information about Web Push Notifications.
Sign in to comment