1590156 - Web Push quota incorrectly decrementing on user displayable notifications

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[JR Conlin [:jrconlin,:jconlin]]

A user is reporting an issue with Webpush messages failing to display after a very short period. See https://github.com/mozilla-services/autopush/issues/1356. User reports that the about:serviceworkers page is showing the endpoint URL to be NULL and believes this may be due to the quota system disabling the subscription even if there are notifications being displayed to the user.

Comment 1

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

I don't think we will address this in Fennec, but I am pointing the A-C team to this bug to make sure we do the right thing in Android-Components / Fenix.

Comment 2

[Jonathan Almeida [:jonalmeida]]

For the sake of documentation, we have a way to mitigate this from occurring to the best of our ability in android-components/fenix:

A user agent pings the autopush servers on start-up once every 24 hours to check that our push subscriptions are still valid and notifies the client apps by the onSubscriptionChange push events to do the appropriate re-registering for push subscriptions. This the best way for clients to ensure they have active subscriptions.

In the short term, we need bug 1611035 to be fixed in order to deliver web push messages to clients on a cold boot, but that shouldn't block client apps from ensuring that they are re-registering for a push subscription on the appropriate callback.