Edge on Android and push subscription

Question

Edge on Android and push subscription

Meelis Lilbok 76

Hi,

try 
{     
	// Subscribe the user to push notifications     
	pushSubscription = await serviceWorkerRegistration.pushManager.subscribe
	({       
		userVisibleOnly: true,       
		applicationServerKey: urlBase64ToUint8Array("YOUR PUBLIC VAPID KEY HERE")     
	});   		
} 
catch (err) 
{     
	// The subscription wasn't successful.     
	console.log("Error", err);   
}

On Android, pushSubscription.endpoint is always https://permanently-removed.invalid/......

Permission is "granted", sw is registered and OK.

Edge version 143.0.3650.97. Xiaomi 12TPro. Android: 15.

Regards
Meelis

Michael Le (WICLOUD CORPORATION) 11,080 Reputation points Microsoft External Staff Moderator

2026-01-15T10:25:44.6166667+00:00

Hello @Meelis Lilbok , my apologies for the ping. Do you have any update on this issue?
Vinicius 20 Reputation points

2026-02-19T19:37:42.69+00:00

I have the same issue. Works on every single browser except edge android. Tested on Edge, Edge Beta and Edge Canary. All of them are broken.

Also tested with PWA installed. Broken as well.
JakobStrm-2195 11 Reputation points

2026-02-19T20:48:08.3333333+00:00

Exactly... All other browsers work fine..
Stuff like this really takes away the experience. Microsoft needs to either fix this, or tell us why they wont. Otherwise i think i will just change browser back to chrome on both desktop and mobile. This is silly..
Vinicius 20 Reputation points

2026-02-19T21:01:02.52+00:00

I made a post here with some test data https://learn.microsoft.com/en-us/answers/questions/5781524/microsoft-edge-edge-beta-on-android-are-not-receiv?page=1&orderby=Helpful&comment=answer-12604035&translated=false#newest-answer-comment

1 answer

Your answer

Michael Le (WICLOUD CORPORATION) 11,080 Reputation points Microsoft External Staff Moderator

2026-01-15T10:25:44.6166667+00:00

Hello @Meelis Lilbok , my apologies for the ping. Do you have any update on this issue?
Vinicius 20 Reputation points

2026-02-19T19:37:42.69+00:00

I have the same issue. Works on every single browser except edge android. Tested on Edge, Edge Beta and Edge Canary. All of them are broken.

Also tested with PWA installed. Broken as well.
JakobStrm-2195 11 Reputation points

2026-02-19T20:48:08.3333333+00:00

Exactly... All other browsers work fine..
Stuff like this really takes away the experience. Microsoft needs to either fix this, or tell us why they wont. Otherwise i think i will just change browser back to chrome on both desktop and mobile. This is silly..
Vinicius 20 Reputation points

2026-02-19T21:01:02.52+00:00

I made a post here with some test data https://learn.microsoft.com/en-us/answers/questions/5781524/microsoft-edge-edge-beta-on-android-are-not-receiv?page=1&orderby=Helpful&comment=answer-12604035&translated=false#newest-answer-comment

Answer 1

Hi @Meelis Lilbok ,

Thanks for reaching out.

From your description and the code shared, the behavior you’re seeing does not appear to be caused by an issue in your implementation. Your usage of the Push API (pushManager.subscribe(), notification permissions, service worker registration, and VAPID keys) follows the standard flow described in Microsoft’s official Edge documentation:

https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps/how-to/push

On Edge for Android, pushManager.subscribe() can still complete successfully and permissions may show as granted, even though Web Push delivery may not function as expected on this platform. Because of this, Edge on Android can return a placeholder endpoint such as https://permanently-removed.invalid/... instead of a real push service URL.

This placeholder endpoint indicates that while the subscription call itself succeeds, the browser does not expose an actual push endpoint that can be used by a server to deliver notifications. In practice, this means push subscription appears to work, but push messages cannot be delivered on Edge for Android in this scenario.

What you can try next:

If Web Push notifications are a core requirement, consider testing with another Android browser where Web Push is known to work.
You may also want to install the site as a PWA and verify whether push behavior differs when running in the installed app compared to the regular browser.
For Edge on Android users, consider providing a fallback notification approach instead of relying solely on Web Push.
Since this behavior is platform-related, keeping an eye on future Edge for Android updates may also be helpful.

Your service worker registration, permissions, and VAPID configuration are not the root cause here - this behavior appears to be related to how Edge on Android currently handles Web Push, rather than an issue with your implementation.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Meelis Lilbok 76 Reputation points

2025-12-30T09:30:35.5833333+00:00

Hi Jack!

Thanks for your reply!

Same code works fine with Google Chrome on Android and also with Edge on Windows Desktop. Installing as PWA - same problem.

Digging further. :)

Regards,
Meelis
Jack Dang (WICLOUD CORPORATION) 14,955 Reputation points Microsoft External Staff Moderator

2025-12-30T09:37:28.33+00:00

Hi @Meelis Lilbok ,

Thanks for your feedback!

If you find my answer helpful, consider following the instructions here so others with the same problem can benefit as well.

Happy Holidays!
JakobStrm-2195 11 Reputation points

2026-02-11T14:07:19.75+00:00

Having the same issues.. And a couple of years ago it worked fine.
To be honest i am a little suprised that this does not get resolved by Microsoft?
Vinicius 20 Reputation points

2026-02-19T19:35:53.15+00:00

I am having the same issue. Unbelievable that this has been broken for so long.

Share via

Edge on Android and push subscription

1 answer

Your answer