Glad to hear that @louiscuvelier
Thanks for the confirmation!
Hi @arunbasillal,
I didn’t notice it after the update, but the error is back. It’s odd because, when I made a « Forced refresh » and I navigate between my pages, it’s fine, no errors.
But, when I close the tab in Chrome and I reopen my website, the error is back …
When you gave me the file before the update, it was working well.
Thanks for your help.
Hello again @louiscuvelier
I just tested on Chrome as you said (made sure sw is installed, closed tab and reopened) and all that and couldn’t see the Uncaught SyntaxError: Unexpected token < error.
Did you change something since the post? Do you still see it?
Hello @arunbasillal,
Yup I still have the issue and even on Chrome on another computer.
But it’s no more Uncaught SyntaxError: Unexpected token <
I have net::ERR_BLOCKED_BY_CLIENT on AdSense script but only when the website was cached once with Super PWA.
Hello @louiscuvelier,
Good day! Can you please let me know whether you are using any Adblocker extensions on your browser?
Thanks,
Jose
SuperPWA
Thanks @louiscuvelier,
Can you please delete the AdBlock from your browser completely and try again. (Don’t forget to clear your cache & delete cookies and other site data.)
We’ve tried upon our systems and cannot find that error.
Looking forward.
Thanks,
Jose
SuperPWA
@josevarghese,
It’s working when I delete AdBlock.
I tried with the previous version of Super PWA that you manually gave me in this topic and it’s working great with AdBlock.
Thanks @louiscuvelier for the instant reply and glad to know that the none of the errors are their once the AdBlock is deleted.
I think my teammate @arunbasillal can explain more about the previously gave version (manually) and why we changed it.
Thanks,
Jose
SuperPWA
Hello @louiscuvelier
The previous version I gave you blocked out all external urls.
However, I noticed that many external resources can be cached (such as Google fonts) and for the benefit of such things, I made a modification where only resources that explicitly send the do-no-cache (over simplifying it) header are excluded.
net::ERR_BLOCKED_BY_CLIENT is not an error, even though it shows in red. Or we could say its a known error. As it doesn’t affect the performance of the website in any way, and is induced by a Chrome extension, it can be safely ignored.
Hope that makes sense.
Hello @arunbasillal,
Thanks for your explication. But, you should consider to add Google AdSense for no-cache. It’s my problem actually (and I assume, not only mine).
This is the link : https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
