In the end I tried something relatively simple that finally solved the problem:
#GALAXY TAB BROWSER CACHE CLEAR UPDATE#
This time (August 2019) the CSS file version number update no longer sufficed, nor did some of the simpler measures mentioned here work for me, or I couldn't even find access to some of them (on a borrowed android phone). (should be done in every html file of the site)) (example: link rel="stylesheet" href="style.css?v=001" where you upgrade this pseudo-version number every time you make a change to a CSS file, e.g. And that even though I had already employed the version-number-trick in the CSS file-call in the head section of the html which had helped me avoid these pesky aggressive cachings in the past. My latest CSS would however not be applied apon refresh. This trick can refresh the CSS file, at least in Android's blue-globe-iconed default browser (but quite likely its twin, the official Chrome browser, too, and whatever other browsers we encounter on "smart"phones with their trend of aggressive caching).Īt first I tried some of the fairly simple solutions shared here, but without success (for example clearing the recent history of the specific site, but not months and months of it).
![galaxy tab browser cache clear galaxy tab browser cache clear](https://techshali.com/wp-content/uploads/2018/06/clear-cache-galaxy-a6-plus.jpg)
In short: Create a temporary html file copy and browse to it to update the CSS cache. Today, a fairly simple developer-side solution worked for me when the caching problem was a cached CSS file.
![galaxy tab browser cache clear galaxy tab browser cache clear](https://images.samsung.com/is/image/samsung/p5/uk/support/mobile-devices/how-do-i-clear-the-cache-on-my-galaxy-a5/images/how-do-i-clear-the-cache-on-my-galaxy-a5-3.jpg)
Here is another simple solution that may work when others fail: