You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cf50a64
Browse filesBrowse the repository at this point in the historyBrowse files
fix: service worker revalidates pages too; version + Reload app in Settings (0.12.3) (#326)
0.12.2 sent pages as no-cache, but the installed iOS app still showed the old
build: its service worker fetched pages with a plain fetch(), which let the
browser hand back the copy it already held (cached under the old
stale-while-revalidate header for up to a year).
- public/sw.js (cache v3): page loads use fetch(request, { cache: 'no-cache' })
so the browser always checks with the server (a 304 when unchanged), and the
offline shell is precached with cache: 'reload'.
- When a new worker takes over, the app reloads into it once (controllerchange),
or offers the Update toast if a draft, voice mode or a call is in progress.
- Settings shows "Version <build id>" with a Reload app button: the installed
app has no reload button, and this says which build is running.
Tested in Chromium on a standalone production build: old v2 worker replaced by
v3, the open page reloaded exactly once, pages then load through the worker
(200), and offline still falls back to the cached shell.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments