Web Push API: Not able to subscribe AbortError

Issue #19173729 • Assigned to AA


Levin R.
Oct 2, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 6 people

Sign in to watch or report this issue.

Steps to reproduce

I’m not able to subscribe to push notifications.
The .subscribe()-method just throws an AbortError. It’s working fine in other browsers like Firefox and Chrome.
I could only find https://stackoverflow.com/questions/50781947/edge-17-pushmanager-subscribe-fails-with-aborterror online which sadly didn’t help.
Am I missing something or is it broken?


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

    • Also happening in 44.17763.1.0

    • Microsoft Edge Team

      Changed Assigned To from “Venkat K.” to “AA”

    • Thank you for filing this bug, Levin. Would you mind providing a sample or site that is experiencing this issue so that we can take a look?

    • Hey there. I already was in contact with Kyle Pflug (according to LinkedIn he’s Senior Program Manager for MS Edge) on Twitter sending him details on how to access an example app where I experiencing this issue. Maybe check with him. I cannot publish the details publicly.

    • He can use the Microsoft’s demo website https://webpushdemo.azurewebsites.net/ used to promote Web push API support (lol.)

    • Same problem here. Notifications used to work in the past, but now Edge seems broken and throws an error when you try to subscribe. The error is [Object DOMException]: { code: 20, message: "AbortError", name: “AbortError” }. You can reproduce the problem by visiting https://pushpad.xyz and trying to subscribe to notifications. When you click the Subscribe button or the Bell you get the permission prompt, then you say Yes, but an AbortError is raised. Note that Pushpad is working fine on all other browsers. Please fix this issue.

    • Same problem here. Pls fix.

    • Bump. Same problem here. Are there any solutions?

    You need to sign in to your Microsoft account to add a comment.

    Sign in