Open yjbanov opened 3 years ago
I wonder if we should just remove non-core caching for now?
Wouldn't that effectively kill offline support?
Err, I guess we could switch that to online-first instead
good point
What worked for me was to create a new request from event.request
, and setting the init object to { 'cache': 'no-cache' }
, when fetching from the server in the service worker's fetch event handler.
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
https://github.com/flutter/flutter/pull/75535 fixed application and service worker versioning issue. However, reportedly there's still an issue with us loading stale resources when the app is updated. Our tests may not be covering this, so we should revisit this specifically and make sure this is covered by tests.