-
Notifications
You must be signed in to change notification settings - Fork 307
Edge - *always* gets 401 Unauthorized #209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, We can send notifications to Edge using this library. Windows had some bugs on older versions. We can send push to Windows Version 1803(OS Build 17134.407) successfully. Can you get any other notifications from other websites (for edge browser) on the same device ? Is it possible to try web push on new windows and edge versions ? |
I would love to test by myself, but the thing is that I never succeeded actually subscribing on Edge, in every Windows 10 version I've had so far. I'm currently on the latest stable version of Windows (October upgrade + updates). Here's a bit of code that works for ALL browsers except Edge:
And I simply get an "AbortError" (in the "catch" block), and I have no clue why...
I've tried many different examples, even one provided by Microsoft/Edge themselves. |
@nunoperalta This is a known bug that can be reproductible on their own demo website |
I realize this is not actually related to this project, but has anyone managed to get it working on Edge in some way? |
Setup
Users seem to be using Microsoft Edge 17.17134 on Windows 10
When sending notifications, always get back:
"Client error:
POST https://dm3p.notify.windows.com/w/?token=(...)
resulted in a401 Unauthorized
response"Notification to be sent successfully
Features Used
Example / Reproduce Case
I receive from user:
{"endpoint":"https://dm3p.notify.windows.com/w/?token=<348 chars>","expirationTime":1551451893000,"keys":{"auth":"<22 chars>","p256dh":"<87 chars>"}}
Content Encoding: aes128gcm
This is properly saved in database, so it's not the same issue as #174
Same code works well for all other browsers:
The text was updated successfully, but these errors were encountered: