You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.
I came here from https://webpushdemo.azurewebsites.net/ which I found when looking for a solution to why my push notifications are not working in Edge on Android.
However, even the demo itself does not work on my Android phone! No notifications are showing up after pressing "Initiate push" and approving push notifications. It seems to work fine in other browsers.
I am testing on
Nokia 8.1, Android 10, Edge 45.03.4.4955
The text was updated successfully, but these errors were encountered:
Will it ever been solved?
The notification arrives to Edge Mobile, but without payload. Even with the encryption, it arrives, but with the exception that the message should be long at least 104 bytes. As the payload is still missing.
The Microsoft server accepts the request without any error message and forward an empty push notification to the mobile browser without any error, warning or log possibility.
But as said... It seems that the mobile team of Edge doesn't exist anymore.
Edit: it is funny that the this paid service is working on Android and Edge: www.onesignal.com
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I came here from https://webpushdemo.azurewebsites.net/ which I found when looking for a solution to why my push notifications are not working in Edge on Android.
However, even the demo itself does not work on my Android phone! No notifications are showing up after pressing "Initiate push" and approving push notifications. It seems to work fine in other browsers.
I am testing on
Nokia 8.1, Android 10, Edge 45.03.4.4955
The text was updated successfully, but these errors were encountered: