Firefox for Android doesn't deliver every push notifications

[gyaaniguy]

NOTE: Please test in a least two browsers (i.e. Chrome and Firefox). This
helps with diagnosing problems quicker.

Please confirm the following:

• I have read the README entirely
• I have verified in the issues that my problem hasn't already been resolved

Setup

Please provide the following details, the more info you can provide the
better.

• Operating System:
  PHP 5.6.30
• web-push-php Version: latest as of this date

Please check that you have installed and enabled these PHP extensions :

YUP

Please select any browsers that you are experiencing problems with:

• Firefox for Mobile
  54.0.1 - android 4.2

Problem

firefox for android doesn't work with default setting. Works when $webPush->setAutomaticPadding(false); is set .

Errors with the default setting, Haven't checked other values, but the default fails with a 410 error

["message"]=>
string(427) "Client error: POST https://updates.push.services.mozilla.com/wpush/v2/gAAAAA..........M-yXA resulted in a 410 Gone response:
{"code": 410, "errno": 999, "error": "", "more_info": "http://autopush.readthedocs.io/en/latest/http.html#error-codes",

Expected

to return true.

Features Used

• VAPID Support

Example / Reproduce Case

function webPush_Register() {
$authPush = array(
'VAPID' => array(
'subject' => 'https://coinvalue.me',
'publicKey' => PUBLICKEY,
'privateKey' => PRIVVATEKEY
),
);
$webPush = new WebPush($authPush);
// $webPush->setAutomaticPadding(false); // disable automatic padding
return $webPush;
}

Other

Thanks for the library :)

[Minishlink]

Hi, thanks for your feedback. :)

The value indicated here might be outdated. Maybe try with setAutomaticPadding(X), where X < 3052?

[gyaaniguy]

setAutomaticPadding(3050) - Returns same error

setAutomaticPadding(2000) - Sends notification. No errors.

In my case I can keep it disabled. so no issues for me.

[Minishlink]

With hindsight, I don't think the length of automatic padding is wrong here. You would have received a 413 error. It looks like a sync problem through the GCM bridge (maybe when payload is too long it takes too much time??).
Another dev had a similar issue, see #90. But it seems his bug was resolved.

Let's ping @jrconlin, he may have more insight :)

[deb00t]

Hi guys, just a bump from me. And maybe 5 cents in addition.
I'm actually not using this library, but stumbled across the same problem.
Can't get notifications for Firefox Android to work either - ending up with the same code combination - 410/999

However, there's an error message saying "GCM recipient not available."

wpush v1 url-based tests and examples seem to work both desktop and android. but current FxA and FxA beta both send v2 endpoints to our server, when registering. Same for desktop Fx. HOWEVER, desktop Fx successfully receives server-pushed messages, the android version doesn't.

So there's obviously a problem with automatic bridging of mozilla webpush to GCM/FCM (battery/optimization reasons). I wasn't able to find out, how to configure the request to https://updates.push.services.mozilla.com/wpush/v2/... to receive newly registered FCM ID, or something.

Anyone an idea how to tell Mozilla's server, which GCM it should use?

[jrconlin]

Providing a bit more feedback on this after being contacted this morning.

In short, we weren't able to reproduce the same 410 error that deb00t was seeing, however we did notice some very odd behaviors. Not sure why, but GCM was being unusually slow to deliver messages (as in 4-10 minutes to complete the Webpush QA Page). GCM may be having issues that could be percolating back to our WebPush service.

Granted, slowness like that should not cause the message to fail like what was being reported, but that also comes from GCM (the reply failed items list).

There's not been a change to our server code in quite some time. We'll keep an eye on things, but for now it just may be that sending messages to android apps may not be quite as zippy.

[chrisdeeming]

Just wanted to let you know that the issue as described in the first comment seems to still exist. If I can be of any assistance in helping to debug this @jrconlin or @Minishlink then happy to help.

If the notification is pushed to a Mozilla endpoint subscribed to via macOS, it works fine. If it's a Mozilla endpoint and Android (7) then it fails with a 410 gone err 999 message.

We're working around it by disabling automatic padding for any Mozilla endpoint right now which makes it work for Android:

$webPush->setAutomaticPadding(0);

Which is ok, but obviously we'd rather keep the padding if possible.

Same here. Firefox on Android won't work without

$webPush->setAutomaticPadding(0);

[chrisdeeming]

Sorry for the nudge @jrconlin and @Minishlink but this issue still needs attention. Let me know if I can be of assistance.

[jrconlin]

Going to reopen this to try a patch.

[jrconlin]

I have a guess as to what the problem might be, but I'd appreciate some confirmation before I arbitrarily pick a fix.

In order for messages to get to android, we have to transcode them to GCM format. GCM imposes it's own set of limits on how big a message can be. The max size I calculated we could send was 3070 octets (that's the encrypted message size, not the message body size). To be safe, I'm presuming that @Minishlink trimmed it down to 3052. Since this is a complex system made of many moving parts, things may have changed somewhere reducing the message size further.

How much further is a bit of an unknown. I'm a bit bandwidth constrained right now, so I don't have a lot of time to set up a test PHP rig and keep poking the system to determine the max size that things will allow. I can either pick a new semi-arbitrary message length (3000? 2048?) or I might ask y'all if there's a value that you find works.

Thanks!

attn: @chrisdeeming, @tino-codes