我找到了一个可行的办法，但很难看。

Connect the Android device to your PC with a USB cable and open Chrome on your desktop. Right-click anywhere on a page and select "Inspect". Click the three-dot menu and select "Remote devices" under the "More tools" menu: In the panel that opens, select your device and then the "Inspect" button next to the name of the tab on your phone that needs to be refreshed: In the window that opens, click the "Network" tab and check the "Disable cache" checkbox: Reload the page on your phone or using the reload button in the DevTools window.

注意:如果你的手机没有出现在设备列表中: 确保USB连接使用的是文件传输模式，而不是简单的充电 尝试重新启动ADB或运行ADB设备，看看设备是否被检测到

以隐身模式查看页面将禁用缓存。这是我在不通过设置手动清除缓存的情况下强制刷新样式表的唯一方法。

我一直在为不刷新的CSS文件而挣扎。但是您可以在地址栏中输入CSS文件本身的名称并刷新它。之后就好了。Android 8上的Chrome。显然，如果涉及多个文件，这将是令人厌烦的。

不要忘记确保“减少数据使用”设置是关闭的，因为它似乎下载缓存的数据(从谷歌服务器?)，即使您的本地缓存被刷新。

如果只是包含文件的问题，只需在路径后添加version (?v=12345678)

<link rel="stylesheet" type="text/css" href="style.css?v=12345678" />

无论谁再次加载页面都将看到更改。

这是另一个简单的解决方案，当其他人失败时，它可能奏效:

今天，当缓存问题是缓存的CSS文件时，一个相当简单的开发人员端解决方案对我来说是有效的。简而言之:创建一个临时html文件副本，并浏览到它来更新CSS缓存。

这个技巧可以刷新CSS文件，至少在Android的蓝色全球图标默认浏览器中(但很可能是它的孪生兄弟，官方Chrome浏览器，以及我们在“智能”手机上遇到的具有积极缓存趋势的其他浏览器)。

细节:

At 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). My latest CSS would however not be applied apon refresh. 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. (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. 001, 002, 003, 004... (should be done in every html file of the site))

这一次(2019年8月)CSS文件版本号更新不再足够，这里提到的一些更简单的措施对我也不起作用，或者我甚至无法访问其中的一些(在借来的安卓手机上)。

最后，我尝试了一些相对简单的方法，最终解决了这个问题:

我复制了站点的index.html文件，给它一个不同的名字(indexcopy.html)，上传它，在Android设备上浏览它，然后浏览回原始页面，刷新它(用地址栏左边的刷新按钮)，voilà:这一次，index.html的刷新终于起作用了。

Explanation: The latest CSS file version was now finally applied on Android when refreshing the html page in question because the cached copy of the CSS file had now been updated when the CSS file was called from a differently named temporary html page that did not exist anywhere in the browser history and that I could delete again afterwards. The aggressive caching apparently ignored the CSS URL and went instead by the HTML URL, even though it was the CSS file that needed to be updated in the cache.