Does not work when deployed to a sub-directory

[CharlesOkwuagwu]

I'm able to build and test successfully on my local machine.

I'm unable to get it to work when deployed to a sub-directory on my domain, for example: www.somedomain.com/demo

Please what would i need to change for this to work?

[joewashek]

I am having this same issue. You can work around some of the issues by configuring the PwaOptions to not register the service work and manifest files, and then statically place the link and scripts tags into the html page (_Layout.cshtml).
For example:
<script>'serviceWorker' in navigator && navigator.serviceWorker.register('/demo/serviceworker')</script>

Doing this allowed the service worker to connect, however, during it's load, it tries to find an offline.html file at the root of the website. I'm not sure how to workaround getting the service worker to look for /demo/offline.html

[MemnochDaCoder]

I too am having this issue but even the workaround is not working. I can get the manifest to register when placed in the wwwroot folder but the service worker fails to initialize with the error
Uncaught (in promise) TypeError: Request failed

services.AddProgressiveWebApp(new PwaOptions { CacheId = "LogCacheV1" , RegisterServiceWorker = false, RegisterWebmanifest = true}, "manifest.json");

Is the code in Startup.

Addendum: My issue was bad routes to precached files.

[dayport]

I have this same issue, I feel like this could be easily corrected by making the constants found https://github.com/madskristensen/WebEssentials.AspNetCore.ServiceWorker/blob/master/src/Constants.cs instead use PwaOptions with default values.