Maybe change the maxAgeSeconds of the cache in the service worker will solve the problem:
/**
* Check out https://googlechrome.github.io/sw-toolbox/docs/master/index.html for
* more info on how to use sw-toolbox to custom configure your service worker.
*/
'use strict';
importScripts('./build/sw-toolbox.js');
self.toolbox.options.cache = {
name: 'ionic-cache',
maxAgeSeconds: 60*8,
//maxEntries: 2
};
// pre-cache our key assets
self.toolbox.precache(
[
'./build/main.js',
'./build/main.css',
'./build/polyfills.js',
'index.html',
'manifest.json'
]
);
// dynamically cache any other local assets
self.toolbox.router.any('/*', self.toolbox.networkFirst);
// for any other requests go to the network, cache,
// and then only use that cached resource if your user goes offline
self.toolbox.router.default = self.toolbox.networkFirst;
Did anyone find a solution about this? Iβm having just the same problem with service worker. My app is using a lot of memory in browser and seems is increasing every time I refresh the page. I added the option that @Natanael4354 said, but I think itβs not working right.
This is my service worker right now:
'use strict';
importScripts('./build/sw-toolbox.js');
self.toolbox.options.cache = {
name: 'ionic-cache',
maxAgeSeconds: 60
};
// pre-cache our key assets
self.toolbox.precache(
[
'./build/main.js',
// './build/vendor.js',
'./build/main.css',
'./build/polyfills.js',
'index.html',
'manifest.json'
]
);
// dynamically cache any other local assets
self.toolbox.router.any('/*', self.toolbox.fastest);
// for any other requests go to the network, cache,
// and then only use that cached resource if your user goes offline
self.toolbox.router.default = self.toolbox.networkFirst;