Thanks for reporting this @skilesare. This wonderfully descriptive error message is shown for any exception thrown inside the WASM boundary so we don’t know what exactly is causing that, but we have a new service worker version currently being rolled out that enables better exception handling and this should show a more helpful message.
@ZackDS the error message you’ve posted looks like a connection issue with the boundary nodes. I’ll ping the relevant team.
@peterparker the issue you posted is caused by either a replica that’s running behind, or a device that’s ahead.
I’m confident that these are three independent issues. The original is on Saturday, ZackDS’s is from Thursday and peterparker’s is from Sunday.
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.
The DecompressionStream was added with the goal of reducing the size of the service worker, which polyfills would not help since we would still maintain the bigger bundle size with it.
We are discussing the possibility of alternatives already though (e.g. polyfills) since we missed the fact that it was added only in Q1/2 2023 for Safari and Firefox respectively. Note that according to browser stats, 84.59% of global users have versions that support that API already, in terms of comparison this is 9.58% lower then supporting service workers themselves which is currently at 94.17%.
Thank you, the problem is solved after updating the system, but updating the system is not what I want. But still very grateful, hope this little bug can be fixed, so it will be very friendly to ordinary users like me