Browser issue PUSH doesn't work on win7

[Alpha1]

Affected version

2.1 beta

 

[Mike]

Can you confirm the exact browser details? Are you using Firefox ESR?

 

[Alpha1]

Firefox 63.0.1
No ESR.

 

[rdn]

Windows 7 SP1
Google Chrome is up to date
Version 70.0.3538.77 (Official Build) (64-bit)

Works fine for me.

 

[rdn]

Windows 7 SP1
Firefox 63.0.1 (32-bit)

Works fine also.

 

[TickTackk]

I think it must be the privacy settings in about:config which is known to do weird stuff because the similar bug happened even for me but once I turned it off the issue was gone.

 

[Mike]

In about:config, what are the values for dom.serviceWorkers.enabled and dom.push.enabled?

 

[ibnesayeed]

Firefox might not allow enabling notifications in the Private Browsing mode. As far as i know, some features like Service Workers are not enabled in Private Browsing mode, so notifications could be one of those.

 

[Alpha1]

In about:config, what are the values for dom.serviceWorkers.enabled and dom.push.enabled?

default, boolean, true
for both.

 

[Floyd R Turbo]

Same here, Win 7, FF 63.0.1, can't activate push

 

[Alpha1]

Im on 64bit Windows 7 Pro SP1 btw.

 

[BassMan]

Using W10, FF 63.0.1, push enabled, just got 2 alerts, but it doesn't work...

Ah, kill me... It works... Sorry, I'm sick... time to sleep...

 

[duderuud]

Can you confirm the exact browser details? Are you using Firefox ESR?

Didn't work here, thought it was my ESR and indeed...installed normal variant and it worked again.

 

[Floyd R Turbo]

I can confirm that it's possible to enable push notification in Win7 using Chrome. Firefox appears to be the problem, not Windows 7.

 

[Alpha1]

Yes, I am getting the notice and the enable button on Chrome. Not FF.

 

[Chris D]

I have added a bit of error logging on top of what we already log, so I'm hoping that if you both @Floyd R Turbo and @Alfa1 go to Preferences with your F12 Developer Tools console open then hopefully you'll have some useful information there.

 

[Alpha1]

Console has this:

unreachable code after return statement[Learn More] js:83:1788
unreachable code after return statement[Learn More] js:143:462
unreachable code after return statement[Learn More] js:143:506
unreachable code after return statement[Learn More] js:143:462
unreachable code after return statement[Learn More] js:83:1788
unreachable code after return statement[Learn More] js:143:506

Service worker error TypeError: "ServiceWorker script at https://xenforo.com/community/js/xf/service_worker.js for scope https://xenforo.com/community/js/xf/ 
encountered an error during installation." core-compiled.js:120:34
a/<https://xenforo.com/community/js/xf/core-compiled.js:120:34 

navigator.serviceWorker.register threw an error. core-compiled.js:174:380 
registerWorker/<https://xenforo.com/community/js/xf/core-compiled.js:174:380 
a/<https://xenforo.com/community/js/xf/core-compiled.js:120:77

 

[Chris D]

Ha... this is kind of annoying. I think I had this same issue, a while ago as my search just turned this up which I apparently viewed before.

There's potentially two different solutions this one and this one.

The second one there is probably the easiest to do.

It's worth noting that this could be a side-effect of having multiple Firefox versions installed (either now or in the past) such as stable + beta etc. and they've used/are using the same profile.

Let us know which of those (if any) work for you.

 

[Alpha1]

Yes, I had nightly installed before. Refreshing worked fine. Problem is that end users will not work this out.

 

[Chris D]

Not a lot we can do about that though, unfortunately. It appears to be a Firefox quirk.