Answers
1 answer
That usually means the regular browser profile is still controlled by an older service worker or its Cache Storage, while incognito starts with a clean profile. A hard refresh is useful for the normal HTTP cache, but it doesn't guarantee your PWA will stop serving a cached response through a service worker. Check DevTools > Application > Service Workers: if a newer worker is "waiting," it won't take over until every tab or window it controls is closed, unless your update flow deliberately uses `skipWaiting`. Also check cache names and your fetch strategy: deploys should use a new versioned cache, reference hashed assets, and remove obsolete caches during `activate`. For a quick diagnosis, use DevTools' "Bypass for network" or unregister and clear site data. If that shows the current app, the deployment is probably fine and the stale part is the update/cache lifecycle.
Your answer
Sign in to answer.
Keep exploring