I have a service worker going fine in Chrome desktop and Chrome mobile, and I can tell exactly what is happening via the amazing DevTools in Chrome desktop (monitoring Chrome mobile remotely via USB). My service worker is based very closely on this example. The page reloads fine without a network connection, and from the Network tab of DevTools I can confirm that resources are being cached and served by the service worker as expected.
But I am also loading the same page in a WebView and I’m struggling to determine whether the service worker is actually registering properly and operating as it should. I can’t see a way of debugging this in the same way as you can with DevTools in Chrome desktop/mobile.
What is certain is that the page doesn’t reload without a connection when it is in the WebView, so some resources aren’t being cached. This is despite the fact that service workers seem to be supported in WebView.
Looking around the place for possible steps or settings I might be missing to get it working as it does in Chrome, I came across ServiceWorkerController and ServiceWorkerWebSettings, but cannot find any documentation or examples for these (other than the basic docs linked). A search on StackOverflow for these terms gives zero results.
Is there a working example somewhere of a WebView that loads a page with attached service workers? Any idea how to use the above two classes… are they actually necessary?
This is only a partial answer, but hope it helps some anyways:
From what I can tell, the
The Java implementation is a singleton which persists and affects all WebViews in an application, and its only method is to intercept requests via
shouldInterceptRequest. It is very similar to
WebViewClient, the latter of which has more functionality and only affects the WebViews it is attached to (via