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%20noopener%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%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
Highlighted
Occasional Visitor

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)"

1 Reply
Highlighted

@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