Hey folks - apologies for the inconvenience. Like @NathanosDev these are likely different issues.
The issue pointed out by @skilesare is related to an upgrade to the service worker. After the new version of the service worker loads, it fails to load the WASM for response verification.
This can be fixed by simply refreshing the page which will require the service worker to reload and load the WASM properly.
This is not the first time we run into issues with the service worker loading the wasm after an upgrade, so to avoid future issues, we are going to be bundling the WASM into the service worker.