service worker doesn’t register cache and Promise Rejection

  • Resolved priv82465

    (@priv82465)


    6 years, 6 months ago

    In Console of Developer Tools (Chrome) appears “SuperPWA service worker ready”, but when refresh the page with offline doesn’t fetch anything.

    Also, with Web Inspector (Safari) appears in console “Unhandled Promise Rejection: TypeError: Cannot update a null/nonexistent service worker registration”

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

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello @priv82465,

    Good day and thanks for using our plugin SuperPWA.

    I gone through your website and noticed that Icons which you added upon our settings page are responded with a status of 404 (Not Found).

    https://findmecommunity.com/fc/wp-content/uploads/iOS/192×192.png and https://findmecommunity.com/wp-content/uploads/iOS/512×512.png

    Can you please check whether the Icons are their within your Media Library page or not.

    Thread Starter priv82465

    (@priv82465)

    My bad!

    Now isn’t appear that error in my console, but doesn’t still work the offline mode. ?Is it maybe a conflict with another plugin?

    Thanks for your reply. Now I noticed that you have installed the WordPress within a sub folder called fc and noticing some redirects.

    As within the Service Worker generated, your Start Page and Offline Page is set as https://findmecommunity.com/fc which is redirecting to https://findmecommunity.com/fc/ I think the error is because of that. Can you please change the Start Page and Offline Page within our settings page to know how it turns out?

    Hey again,

    Did you get a chance to look into this @priv82465?

    Thread Starter priv82465

    (@priv82465)

    So sorry for doesn’t reply your message. I was trying another alternatives because I though the problem seems around the server itself.

    I’m not good enough talking in english but I’ll try to explain me about my attempts to fix it:
    First of all, if I try to change the start page it doesn’t matter because the redirect affect directly into the “scope” of the manifest. So, the manifest take the directory of the wordpress, in that case /fc and the plugin take that information as “/fc/fc” so in the PWA load the 404 fallback page because that page doesn’t exist (and error log appears, and also the service worker avoid the try to fetch).
    So, editing the superpwa-manifest.json in the start_url and scope erasing the /fc just putting the root page, the service worker starts to work and fetch the content at first sight; even doesn’t show the offline content.
    I was checking out and it seems that it stays in loop around line 18 of the superpwa-sw.js and the collateral damage is don’t update the content of the page until deactive the plugin or edit the manifest again.

    The easy way to fix it is change my directory of wordpress to root; but that’s an security protocol of my client and I can’t change it *sigh*…
    Do you see any solution in someway?

    This has been an issue for a few of our users, so we are looking into alternate ways. Nothing is available at the moment.

    I’ll update this thread when there is one.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘service worker doesn’t register cache and Promise Rejection’ is closed to new replies.