This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 57.99999999999999%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
I am getting this integrity issue only with mobile browsers and android webview (Xamarin forms).
I built an application using Blazor WASM service worker also implemented. I created a wrapper/webview application using Xamarin Forms for this Blazor app.
Now, application is working fine in desktop browser like Edge and Chrome but getting integrity issue with mobile browsers and also in android webview.
I googled and found many answers on Stackoverflow but nothing works for mobile browsers, but those answers solved my problem with desktop browsers.
Here is a screenshot of output window in XF Android
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 40%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYL%3C/text%3E%3C/svg%3E)
It could be caused by the old hash values of service-worker-assets.js is cached by the browser.
The workaround from this issue Blazor WASM Caching problem leading to service worker update problems could be helpful for you:
navigator.serviceWorker.register('/service-worker.js', {updateViaCache: 'none'}); //Provided by dvallmen.
If it doesn't work for you, could you please provide the link to us for testing?
May I know whether your issue has been solved or not? If not, please share it in here. We can work together to figure it out.
Thanks @Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) for guide me and follow up. I made the suggested changes and today I will deploy a new build. If it will not resolve, then I will share test URL with you for further investigation.
Hi @Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) I tried what you suggest but it does not work for me.
Here is the test URL: https://jigsaw-ma.azurewebsites.net/
Log in email: ****
Password: ****
Login PIN: ****
Please check and let me know if you need anything else.
Thank you!
Thank you for your feedback, in order to prevent your personal privacy leakage, I will edit your response, please understand.
I've tested your link on the Android pixel5 emulator with API 30,31 and 32 in Microsoft Visual Studio Community 2022 (64-bit) - Preview Version 17.4.0 Preview 2.1, but it works fine on those Android platforms.
Does this issue occur if you use another emulator or device for testing?
I have found that deleting the "bin" and "obj" directories and doing a rebuild before deploying my Blazor WASM PWA app to production prevents this problem.
Right but not always helpful. This solution solved problem with desktop browsers, but I am getting this issue with mobile browsers and Android webview.