Uncaught (in promise) PushError: permission request declined

[vladyn]

I've got promise rejection in Chrome (Version 60.0.3112.113 (Official Build) (64-bit)) on Windows 7. This is on the landing page, where the Demo button is.

[bhaidar]

I started having the same issue too. Chrome 60.x on Windows 10.

[ak868308]

Try this

Push.config({ serviceWorker: '//serviceWorker.min.js'});

[imRohan]

Has this been fixed? I'm seeing the same error on Chrome Version 62.0.3202.75 (Official Build) (64-bit) ib Windows 7

Edit: Fixed by added a SSL Cert

[visionding]

I have the same error on Chrome 63.0.3236.0 (64-bit) Windows 10

[bradleybensmith]

I'm getting this too. It worked fine on localhost, but is failing in production. I tried the serviceWorker and no change. I manually added my production domain to the allowed list, and still same error.

[newmandani]

Chrome 62.0.3202.89 (Official Build) (64-bit) Incognito mode:

Normal mode:

and some time:

[ommeirelles]

I was having the same error as @bram1028. Worked fine in firefox and chrome localhost but in chrome production got the error. Strange that last week was working just fine for me. I resolved the error by accessing my production through https. Looking for serviceWorker tutorial from google they say that is only possible use it in productions through https..

[projct1]

Same issue with Version 62.0.3202.94 (Official Build) 64 bit Windows 10. http://joxi.ru/l2ZVP4EH8GyWR2 http://joxi.ru/a2XeBzEUyok57A

[ghost]

Hi, it's not an code error. Since new Chrome version Notification have to bieng use by "Secure Origins". So, if you want use Notification http address muste be : localhost OR https://

I you want you cant also start chrome with cmd line with this line : -unsafely-treat-insecure-origin-as-secure="http://example.com"

You can try Notification via native Html5 : new Notification("hello")

Have a nice day.

More info here : https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-powerful-features-on-insecure-origins

[projct1]

Yea, thanks, problem was solved by move to https.

[shahab2058]

The demo given on the https://pushjs.org/ page has the same issue mentioned in the title. I am facing the same issue.