20

I have a Blazor app that I'm deploying to Azure for some alpha testing. I've managed to do this and I can run the app from the website just fine.

The problem comes when I make changes to the client and server projects and republish them. Whatever browser is running the client will run whatever is already in the browser cache until the browser history is cleared. That means until the history is cleared the app appears broken because the client requests on the old version don't match the new server API - not to mention my client side changes don't get tested.

How can I force a reload of the client when I publish my changes? Do I have to tell the browser not to cache my app (not sure how on blazor) and take the performance hit until my app stabilizes? Or is there a way to force a client reload after the first API call using some middleware or something?

Or am I missing something?

Edit: It may be relevant that I used the PWA template provided in Blazor WebAssembly 3.2.0 Preview 2. I'm still running the app from a browser, but it seems possible that enabling the PWA option changed the behavior of the app even when running it as a regular website.

John Christopher Linstrum
  • 363
  • 1
  • 4
  • 11
  • Update for .net6 - I faced a similar issue. My published updates did not appear to work in the install PWA. When debugging the PWA in the browser, I saw 2 offline caches. Both the old version and the recently published files even after starting and restarting the PWA. – Gary Chan Jul 17 '22 at 21:21

7 Answers7

16

Since your app is a PWA, you can declare a js file for registration in the navigator.serviceWorker object. This my.js file can contain a const CACHE_VERSION = 1.0. Updating this value should force the client to download the latest files. See Jeremy Likness' blog post for more info.

Ryan Hill
  • 1,821
  • 2
  • 8
  • 21
5

If anyone looks solution for Azure Pipelines and Azure Static Web App deployment, here is what worked for me:

  1. Added following line on top of service-worker.published.js file.

const CACHE_VERSION = '{#CACHE_VERSION#}'

  1. Added Bash step to *.yaml file, just change your app location accordingly.
  - master

pool:
  vmImage: ubuntu-latest

steps:
  - checkout: self
    submodules: true
  - bash: 'sed -i ''s/{#CACHE_VERSION#}/$(Build.BuildId)/'' MathApp/wwwroot/service-worker.published.js'
    
  - task: AzureStaticWebApp@0
    inputs:
      app_location: 'MathApp'
      output_location: 'wwwroot'
      azure_static_web_apps_api_token: $(deployment_token)
szczellak
  • 51
  • 1
  • 2
4

if you are working on dot net core3.X PWA app, you can add comment in service-worker.published.js so that when browser will compare its cached service worker with updated one, browser will track the changes and load new one.

Sarang Kulkarni
  • 367
  • 2
  • 6
2

This is an extension to the above solution if you are working with Github actions.

Add following step in .github\workflows\whatever-file-name-you-have.yml

- name: UpdateVersion
    uses: datamonsters/replace-action@v2
    id: sub
    with:enter code here
      files: 'Your.App/wwwroot/service-worker.published.js'
      replacements: '%%CACHE_VERSION%%=${{ github.run_id }}'

I have used {{ github.run_id }} to get a unique-ish value, but you could opt for any other random string either from https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#github-context or bring your own version.

And the main solution lies in editing service-worker.published.js

const CACHE_VERSION = '%%CACHE_VERSION%%'
const cacheName = `${cacheNamePrefix}${CACHE_VERSION}`;
Ranvir
  • 2,094
  • 2
  • 19
  • 26
1

This answer is intended to complement Ryan Hill's answer:

Blazor automatically updates to the newer version (at least in .NET 5, possibly earlier too). This happens when the application is first closed and restarted in ALL browser tabs including the installed app (which is another browser tab).

The following article helped me a lot:
https://learn.microsoft.com/en-us/aspnet/core/blazor/progressive-web-app?view=aspnetcore-5.0&tabs=visual-studio#installation-and-app-manifest-1

Also helpful: https://www.eugenechiang.com/2021/05/22/forcing-reload-of-blazor-client-after-publishing-changes/

Chris Berlin
  • 744
  • 6
  • 15
0

If this is PWA application, you should have service-worker.js file. If you will expand it, you will see service-worker.published.js file.

Open it and find async function onInstall(event) method. Now you should put self.skipWaiting(); just below console.info('Service worker: Install');. It all should look like this:

async function onInstall(event) {
    console.info('Service worker: Install');
    self.skipWaiting();
    //rest of the function code
}

If you are curious what and why, you should read this article, section Update completion after user navigation away from app

For as long as the list of "clients," which are tabs or windows displaying your app, is nonempty, the worker continues waiting. The reason service workers do this is to guarantee consistency. Consistency means that all resources are fetched from the same atomic cache.

titol
  • 999
  • 13
  • 25
  • Use this solution with caution. Keep in mind that if you skip the waiting state, your new service worker will begin handling new requests on a page where previous requests may have been handled by an older version. This has the potential to break things. – Ethan Jul 14 '23 at 13:11
  • 1
    @Ethan I guess you are right. In my case, and I belive it's the same for more folks, service worker code won't change. It's just to make this app PWA. – titol Jul 14 '23 at 19:26
-1

I finally found an answer for this that helped me. If you do not need PWA, you can remove it and Chrome (and probably other browsers) should stop clinging on to an old client even after deleting cache and fully reloading. Because after having done this my Chrome still reloaded it. For my app I do not need to use this caching feature or to be able to install it as an app.

I found the answer here: Blazor Chrome caching issues

How to remove PWA:

  1. Delete the following files from wwwroot:
/wwwroot/manifest.json
/wwwroot/service-worker.js
/wwwroot/service-worker.published.js
  1. Delete this line from /wwwroot/index.html
<script>navigator.serviceWorker.register('service-worker.js');</script>
  1. Delete those lines from your csproj file
<ServiceWorkerAssetsManifest>service-worker-assets.js</ServiceWorkerAssetsManifest>
<ServiceWorker Include="wwwroot\service-worker.js" PublishedContent="wwwroot\service-worker.published.js" />

Also... to actually get rid of the app in Chrome, because I had already loaded it this way, I installed it as an app and then uninstalled the app and removed it from Chrome. That finally got me out of this whole loop with Chrome keeping the app and refusing to fully update it in the browser cache / memory / wherever it kept the app

Kasper Olesen
  • 126
  • 1
  • 11