Web app manifest or service worker do not meet the installability requirements

No matching service worker detected. You may need to reload the page, or check that the scope of the service worker for the current page encloses the scope and start URL from the manifest.

Does not register a service worker that controls page and start_url

Any ideas?

“Web app manifest or service worker do not meet the installability requirements”
and
“Does not register a service worker that controls page and start_url”

I look in the Application Manifest and there are no errors there.

Any ideas?

1 – Manifest start URL is not valid

2 – No matching service worker detected. You may need to reload the page, or check that the scope of the service worker for the current page encloses the scope and start URL from the manifest.

Regarding first error – any page I choose – I got error

Second appears from first error.

Please help to fix it. Does SuperPWA requires jQuery Migrate to work properly?

I would want use a category page in place of home page like start url of the PWA.
Can I do that?

add_filter( 'web_app_manifest', function( $manifest ) {
    $manifest['start_url'] = 'CustomPostCatPageUrl';
    return $manifest;
} );

NB : PWA not working on my website. Looks like a WP Rocket issue, wp.serviceworker is broked. I try to find a solution with them.

Best regards,

I know this has been asked many times but none of those other posts seem to solve our issue, so I ask again.

Our Lighthouse report shows these 3 PWA errors:

Current page does not respond with a 200 when offline
start_url does not respond with a 200 when offline
Does not register a service worker that controls page and start_url

Following other suggestions, what we’ve tried:
– We’ve changed the start page to a different one from the home page
– We’ve made sure both images are sized correctly
– We’ve made sure manifest and js actually load (since it seems it used to be an issue while using nginx). Although they do load, we added the 3 suggested rewrite rules to nginx (we’ve removed them already).
– We’ve excluded /superpwa* from cache

Our setup:
– We’re hosted in a Google Compute Engine instance running Nginx, and behind Google Load Balancer to be able to use the CDN.

For testing purposes, currently all caches are clean and disabled: CDN, Nginx and just in case a couple of WP plugins.

Server information and plugins:
WordPress Version: 5.6
Current WordPress Theme: GeneratePress version 3.0.2
Theme Author: Tom Usborne – https://tomusborne.com
Theme URI: https://generatepress.com
PHP Version: 7.3.14
MySQL Version: 8.0.18
Apache Version: This information is not available.
Active Plugins:

a2System Site Plugin for Depaning.fr (Unversioned)
ACF QuickEdit Fields (3.1.1)
Advanced Custom Fields (5.9.3)
AMP (2.0.8)
AMP Blocks (1.6.3)
AMP for GeneratePress (0.1)
Code Snippets (2.14.0)
Contact Form 7 (5.3.1)
Contact Form 7 Zoho Pro (1.1.3)
Contact Form Entries (1.1.6)
Custom Taxonomy Cleanup (1.0.0)
Debug Info (1.3.9)
GenerateBlocks (1.2.0)
GP Premium (1.10.0)
LiteSpeed Cache (3.5.2) <=== Only used for serving webp images, not for caching. Temporarily disabled for the tests
Nginx Cache (1.0.5) <== just to clear nginx cache from UI. Temporarily disabled for the tests
SecuPress Pro — WordPress Security (1.4.12)
Show Hide Author (2.2)
Super Progressive Web Apps (2.1.3)
Toolset Blocks (1.2.1)
Toolset Types (3.3.10)
UpdraftPlus – Backup/Restore (1.16.42)
WordPress Importer (0.7)
WP Mail SMTP (2.5.1)
Yoast Duplicate Post (3.2.6)
Yoast SEO Premium (15.4)
Yoast Test Helper (1.11)

Any ideas what the problem could be are very much appreciated.

Thanks in advance!

This is the error recieved from lighthouse, I see other people also experience this. This seems to be the only thing preventing my site from full marks to be a PWA. FYI, great plugin

Further examining the issue, I noticed the error message is gone if I visit my website’s URL with the: ?utm_source=superpwa query string at the end. Is this how it should work? I’m testing in localhost SSL environment from browser.

Enabling W3TC causing a whole new issue: ?utm_source=superpwa query string not added at the end of the installed PWA in desktop Chrome.