Web Push notification bug (Edge for Android)

%3CLINGO-SUB%20id%3D%22lingo-sub-1774677%22%20slang%3D%22en-US%22%3EWeb%20Push%20notification%20bug%20(Edge%20for%20Android)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1774677%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20don't%20know%20if%20I%20am%20in%20the%20right%20place.%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20set%20up%20web-push%20notifications%20for%20a%20webpage.%3C%2FP%3E%3CP%3EUsing%20this%20PHP-library%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fweb-push-libs%2Fweb-push-php%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fweb-push-libs%2Fweb-push-php%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20works%20perfectly%20on%20all%20my%20desktop%20browsers%20and%20on%20all%20my%20mobile%20browsers%20(firefox%2C%20chrome%2C%20adblock%20browser)%20but%20not%20on%20Edge%20mobile.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20setting%20up%20the%20endpoint%20and%20keys%2C%20all%20VAPID%20data%20and%20sending%20it%20to%20the%20windows%20push%20service%2C%20I%20get%20a%20successful%20answer%20for%20the%20endpoint.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdb5p.notify.windows.com%2Fw%2F%3Ftoken%3DBQYAAAANEG..%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdb5p.notify.windows.com%2Fw%2F%3Ftoken%3DBQYAAAANEG..%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20the%20problem%3A%3C%2FP%3E%3CP%3EAfter%20receiving%20the%20push%20message%20(it%20is%20always%20submitted%20to%20the%20mobile%20device)%2C%20the%20payload%20is%20always%20null.%3C%2FP%3E%3CP%3EIf%20I%20use%20the%26nbsp%3Baes128gcm%20encryption%2C%20the%20message%20is%20not%20submitted%20to%20the%20webpage%20and%20the%20browser%20report%20this%20error%3A%3C%2FP%3E%3CP%3E%22%3CSPAN%3EThe%20message%20payload%20is%20smaller%20than%20the%20smallest%20valid%20message%20(104%20bytes)%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1774677%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAndroid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EEdge%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1790995%22%20slang%3D%22en-US%22%3ERe%3A%20Web%20Push%20notification%20bug%20(Edge%20for%20Android)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1790995%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F829494%22%20target%3D%22_blank%22%3E%40AdrianoTiger%3C%2FA%3E%26nbsp%3BThanks%20for%20reaching%20out.%20Welcome%20to%20the%20MSFT%20Edge%20Insider%20community!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20looks%20like%20there%20could%20be%20a%20number%20of%20overlapping%20areas%20involved%20here%2C%20so%20I'm%20going%20to%20start%20by%20passing%20it%20along%20to%20our%20Mobile%20team.%20I'll%20let%20you%20know%20if%20they%20have%20any%20insights%20to%20share.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1890377%22%20slang%3D%22en-US%22%3ERe%3A%20Web%20Push%20notification%20bug%20(Edge%20for%20Android)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1890377%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F829494%22%20target%3D%22_blank%22%3E%40AdrianoTiger%3C%2FA%3E%26nbsp%3B%20I%20have%20the%20exact%20same%20issue%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fdid-i-find-a-bug-in-edge-mobile-browser%2Fm-p%2F1661350%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fdid-i-find-a-bug-in-edge-mobile-browser%2Fm-p%2F1661350%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1941348%22%20slang%3D%22en-US%22%3ERe%3A%20Web%20Push%20notification%20bug%20(Edge%20for%20Android)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1941348%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F791711%22%20target%3D%22_blank%22%3E%40petervledder%3C%2FA%3E%26nbsp%3BMaybe%20the%20problem%20is%20that%20Edge%20for%20Mobile%20still%20use%20Chrome%2077.0.3865.116%20instead%20of%20a%20newer%20version.%3C%2FP%3E%3CP%3EBut%20I%20can't%20find%20any%20contact%20or%20Edge%20for%20Android%20support%20anywhere.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20now%20tested%20the%20push%20notification%20on%20many%20browsers%20and%20many%20devices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvery%20browser%20is%20able%20to%20send%20push%20notification%20with%20the%20github%20library.%20Except%20Edge%20for%20Android.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20the%20Microsoft%20server%20accept%20the%20endpoint%20and%20return%20a%20successfully%20code%2C%20there%20is%20no%20way%20to%20discover%20what%20went%20wrong.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20sad%20news%2C%20is%20that%20some%20paid%20push-services%20(like%20%3CA%20href%3D%22https%3A%2F%2Fwww.webpushr.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwww.webpushr.com%2F%3C%2FA%3E)%20works%20on%20Edge%20for%20Android!%20So%20there%20is%20a%20way%20to%20have%20push%20notifications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEDIT%3A%20I%20see%20now%20that%20the%20endpoint%20on%20my%20edge%20browser%20is%20fcm.googleapis.com%2Ffcm%2F...%20and%20not%20one%20from%20Microsoft.%20So%2C%20Edge%20will%20transmit%20the%20notification%20to%20the%20Google%20Server%20and%20it%20could%20be%20that%20Google%20is%20just%20rejecting%20all%20messages%20to%20Edge.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

I don't know if I am in the right place.

I am trying to set up web-push notifications for a webpage.

Using this PHP-library: https://github.com/web-push-libs/web-push-php

 

It works perfectly on all my desktop browsers and on all my mobile browsers (firefox, chrome, adblock browser) but not on Edge mobile.

 

After setting up the endpoint and keys, all VAPID data and sending it to the windows push service, I get a successful answer for the endpoint.

https://db5p.notify.windows.com/w/?token=BQYAAAANEG...

 

Now the problem:

After receiving the push message (it is always submitted to the mobile device), the payload is always null.

If I use the aes128gcm encryption, the message is not submitted to the webpage and the browser report this error:

"The message payload is smaller than the smallest valid message (104 bytes)"

6 Replies

@AdrianoTiger Thanks for reaching out. Welcome to the MSFT Edge Insider community!

 

It looks like there could be a number of overlapping areas involved here, so I'm going to start by passing it along to our Mobile team. I'll let you know if they have any insights to share.

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge

@petervledder Maybe the problem is that Edge for Mobile still use Chrome 77.0.3865.116 instead of a newer version.

But I can't find any contact or Edge for Android support anywhere.

 

I now tested the push notification on many browsers and many devices.

 

Every browser is able to send push notification with the github library. Except Edge for Android.

 

Since the Microsoft server accept the endpoint and return a successfully code, there is no way to discover what went wrong.

 

The sad news, is that some paid push-services (like https://www.webpushr.com/) works on Edge for Android! So there is a way to have push notifications.

 

EDIT: I see now that the endpoint on my edge browser is fcm.googleapis.com/fcm/... and not one from Microsoft. So, Edge will transmit the notification to the Google Server and it could be that Google is just rejecting all messages to Edge.

@AdrianoTiger I just tried the webpushr.com demo page, and that didn't work either. They also don't receive a push message payload (it is null).

@MBachhuber You're right. It doesn't work.

On each paid service I tried. The message arrived only once. Then the payload was null.

When I wrote the message, I tried it only 1 time and I was hoping it was working.

But the bug (probably it is more a problem) is not in the Microsoft server, but in the Google server. It seems that Google is just blocking all push notifications from Edge.

 

I wrote everything I was able to debug and discover in this stackoverflow post:

https://stackoverflow.com/a/65147003/5390321

 

Chromium is in the version 88 now. Edge for Android is still using Chromium v.77.

All push messages are directed to the Google Server. Every browser using Chromium use the Google servers to post messages. But messages from Edge are just removed...

Still no reply or any answer from Microsoft team.

But:
- www.pushengage.com works on Android. Probably it use the Google service... Can't believe they was able to bring it to edge with the standard web API.
- Edge Canary use the new chromium version (91 and 92, not 77). But the browser doesn't generate any Endpoint link, when a subscription is made over javascript.