Joaquín Sánchez

IIRC any request done to another origin shouldn't be intercepted by the sw, you don't need to include any runtime caching: you should handle fetch errors from the app

You can add `mode: 'development'` to check workbox logs in the sw (in your local if you can check against the external api), check also if the responses from the...

can you show the response headers for graphql requests? maybe you've a bug in your app. EDIT: check also if the response is cached or not (I mean, the content)

check if the browser is caching the response in network tab; where is the status (should be 200, you have Date and etag response headers, this is wrong, the browser...

Check also if `if-modified-since` present in the request headers.

How about the content? My suggestion (I use these headers): remove etag adding `Cache-Control: no-cache, no-store, max-age=0, must-revalidate` and `Expires: 0` headers.

Just remove the runtime caching for external api. If the response data is old one, you should have something wrong in your graphql backend or proxy: disabling the PWA works?

if using apollo client maybe you can use these default options in the constructor: ```ts const defaultOptions: DefaultOptions = { watchQuery: { fetchPolicy: 'no-cache', errorPolicy: 'ignore', }, query: { fetchPolicy:...

check if the sdk has some internal flag, check also if the new credentials are sent properly (when changing the profile)

I guess it is a bug in workbox, it is returning the fallback page content, if you just request this another page it is working properly https://vite-pwa-org.netlify.app/guide/register-service-worker.html?xxxx EDIT: we've activated...