Errors in Firefox and Chrome

  • Resolved louiscuvelier

    (@louiscuvelier)


    6 years, 9 months ago

    Hey,

    Thanks for the plugin !

    I have two erros after multiple pages reloads on Chrome and Firefox.
    1. In Chrome (64.0.3282.140) I have this :
    superpwa-sw.js:3 Uncaught (in promise) TypeError: Request method 'POST' is unsupported

    2. And in Firefox (64.0.3282.140), this :
    Service worker event waitUntil() was passed a promise that rejected with 'InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable'.

    • This topic was modified 6 years, 9 months ago by louiscuvelier.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 27 total)

  • Hey @louiscuvelier

    Thanks for using SuperPWA and for your kind words!

    I have opened a GitHub issue for this case and I will fix it in the upcoming update – https://github.com/SuperPWA/Super-Progressive-Web-Apps/issues/6

    I will update you once it is fixed. Thanks for your patience.

    Hey @louiscuvelier

    I have just release version 1.3. It should take care of this issue.

    Please upgrade and let me know how it goes. Thanks!

    Here is the changelog:

    = 1.3 =
    * Date: 10. February.2018
    * New Feature: Added support for high-quality splash screen. You can now set the 512×512 icon for the splash screen of your Progressive Web App.
    * Enhancement: Super Progressive Web Apps now accounts for content updates and will update the cache as you update the website.
    * Enhancement: Improved in-browser service worker update handling.
    * Enhancement: Added automatic upgrade of manifest and service worker on plugin upgrade.
    * Bug fix: Only GET requests are served from the cache now.

    Thread Starter louiscuvelier

    (@louiscuvelier)

    Hey @arunbasillal

    It’s working great ! Thanks !

    But, now I have an issue with Google Adsense, SuperPWA and only Chrome.

    When I first load my page with no cache, ads showed up without errors.
    But, on the second reload (and all others) there is no more ads and an error with the Adsense code snippet.

    Uncaught SyntaxError: Unexpected token <

    It’s odd … Can you do you something ?
    I can give you an Adsense code snippet if you want to test it.

    Thread Starter louiscuvelier

    (@louiscuvelier)

    Hey @arunbasillal,

    Forgot what I said. The problem appears oddly only when Chrome console is opened …
    So, it’s ok ??

    Thanks again !

    @louiscuvelier

    Even with the Chrome console open, does it go away if you deactivate SuperPWA?
    Please do that and kindly let me know if you still see the error in the chrome.

    Thread Starter louiscuvelier

    (@louiscuvelier)

    @arunbasillal

    Yup, it goes away if I disabled SuperPWA, “Clear Site Data” (Inspector > Application > Clear Storage > Clear Site Data) and do multiple reloads.
    So, it seems to be a SuperPWA problem.

    • This reply was modified 6 years, 9 months ago by louiscuvelier.

    Does it show up on a specific page? I tried reloading many pages, I see the Adsense ad, but no error in console yet.

    Any tips on how I can recreate this? My version of Chrome is: 64.0.3282.140

    Okay, I see the error when the browser is offline. Do you see it when you are online as well?

    Thread Starter louiscuvelier

    (@louiscuvelier)

    There was some cache from WP Super Cache when I disabled SuperPWA, so the SW was not served.
    I cleaned the cache. Now, you should see the error on any page of the website.

    PS : Even with WP Super Cache disabled, I still have the error.

    EDIT : I see it online.

    Hello again @louiscuvelier

    Via FTP, please replace the superpwa-sw.js in the root directory of your WordPress install (the same directory as wp-config.php) with the one in here: https://www.dropbox.com/s/7i2lpod3zfjxa94/devenir-superpwa-sw.zip?dl=0

    Please do not save the settings of SuperPWA as that would overwrite this file.

    Please let me know once it is done so that I can test the site again. Looking forward to it.

    Thread Starter louiscuvelier

    (@louiscuvelier)

    Hello again @arunbasillal

    I did it. I also disabled Cloudflare and WP Super Cache, so you can test more easily.

    Everything looks good at my end. No more Uncaught SyntaxError: Unexpected token < errors.

    The only error I see is ERR_INTERNET_DISCONNECTED when I am offline. Which is expected because these are external sources.

    I will include the code I sent you in the next update on the plugin, so you can update safely.

    Please check at your end and let me know. Thanks.

    Thread Starter louiscuvelier

    (@louiscuvelier)

    Yes, it seems be ok.

    Thanks a lot !

    Glad to hear that @louiscuvelier

    Hope you enjoy your Super Progressive Web App! Please share it with your friends and support us if you can ??

    Also feel free to let us know your feedback at any point. We are always looking for ways to improve our plugin.

    Hey @louiscuvelier

    In version 1.3.1 I have added the fix I did for you, but with a minor twist. I tested the same on another website and the Uncaught SyntaxError: Unexpected token < no longer shows up.

    Please update and let me know your feedback. Looking forward to it.

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘Errors in Firefox and Chrome’ is closed to new replies.