You are reading this because you saw something like this in your SuperPWA > Settings > Status
SuperPWA generates (or attempts to) two files to convert your WordPress website into a Progressive Web App. You guessed it, the manifest and the service worker.
These files are generated in the root folder of your WordPress install (the same folder where wp-config.php is) during plugin activation.
To generate these files, WordPress needs folder permissions to write to the root folder. In your host however, WordPress couldn’t do it because your web host has limited the permissions on this folder.
Note how I keep saying WordPress needs permissions and not SuperPWA? This is because SuperPWA uses the Filesystem API of WordPress to handle file generation and deletion. So if WordPress can do it, then SuperPWA can do it too.
The ideal way to resolve this, is to contact your web host. Tell them what is happening and maybe even point them to this article. They know your server and they will know what to do.
It is a relatively simple fix and should be a very common support request to your web host and they should be able to help you out in no time.
Once the permissions are adjusted, remember to deactivate SuperPWA plugin and then reactivate SuperPWA from the plugins list in your WordPress admin.
Pro Tip: Instead of deactivating and reactivating SuperPWA, you can simply visit the SuperPWA > Settings page to check the status. Starting with version 1.8, SuperPWA will attempt to generate the manifest and service worker automatically when you visit the SuperPWA > Settings page, if these files do not exist.
TLDR: Ask your web host to adjust the folder permissions on the root folder of WordPress to 755 and make sure that owner / group is the same as the user / group of the process that runs WordPress. Then deactivate and reactivate SuperPWA.