Hello all,
I'm an engineer at Bardeen.
Our extension makes use of Web Assembly, loaded through webpack experimental native WASM support. The WASM file is included in the zip file.
For most of our users, this works perfectly fine. For some users though we're seeing "Failed to fetch" errors loading the file. The URL of the file is "/<hash>.module.wasm", and we can confirm that the file is present in the zip file uploaded to the Chrome store. Because it's a failed to fetch, there is no other debugging information.
Has anyone seen this error before? Is it a chrome bug? Is it a local issue (disk error, some weird interaction with blockers)?
I would love if anyone has any suggestion on how fix this.
Thanks in advance, and cheers,
Giovanni