PWA offline behavior and troubleshooting
What is available offline?
The worker caches eligible published static assets and supplies an offline page when a navigation cannot reach the server. It does not store forum pages for offline reading. Posts, private conversations, payment flows and administrator screens still need the network.
The 161i worker uses an exact static-asset list and checks responses before storing them. HTML, JSON, private/no-store/no-cache responses, Set-Cookie, Vary: Cookie and authenticated responses are excluded. Non-GET requests are not replayed. Disabling PWA removes its offline fallback after the updated disabled worker takes control.
No install button
- Confirm HTTPS, app enablement and a reachable manifest for your edition.
- Inspect the manifest icon URL and actual file dimensions.
- Check whether the app is already installed and whether the banner was dismissed.
- Look for the browser's own Install/Add to Home Screen command. Browser policy and engagement requirements can suppress automatic prompts.
Old appearance after an upgrade
Allow an online visit so sw.php can be rechecked. Its bytes include the release and enabled state; an unchanged worker URL is intentional. 161i's asset list includes the Starter's assets/forum.css and assets/pwa.css. If an older proxy/CDN response persists, inspect the returned worker version and cache headers before deleting site data.
Inspect safely
In desktop Chromium, use developer tools → Application → Service Workers and Cache Storage. Verify the worker scope matches the board path. Cache names include that path and release. Do not unregister a working worker just to hide the install prompt: push uses the same registration.
Acceptance checklist
- Upgrade a test board and verify the new worker controls it.
- Turn PWA off without changing the release; its own caches should clear.
- Check two sibling installations independently.
- Disconnect the network: an enabled PWA shows its offline page, not saved private content.
- Test installation on the actual target phone; desktop registration alone does not prove a home-screen launch.
Include edition, exact build, browser, board path and redacted console errors in a support request.
