I’m learning the project and PlayCanvas so I may not be able to answer all questions. If anyone has any ideas that could help me resolve the issue then I would appreciate it!
The issue is that the project isn’t displaying at the published primary build link. I get a black screen, aside from the PlayCanvas footer. The Chrome console shows a CORS error for basis.wasm.js
For now I’m not sharing the link and I obfuscated a unique identifier in the screenshot.
We moved to a caching mechanism that allowed us to lower latency and higher speeds. It seems to have caused an issue with WASM modules in particular that we are investigating
nothing yet changed, we are testing it. Could you also check one more thing for us - do you have “preload” field checked for basis.wasm, basis.wasm.js in your assets?
Thanks, all. I made a new build, with “preload” deselected for basis.wasm.js, and there is no CORS error.
Can you say what the best practice should be, regarding the “preload” setting and this issue? Am I correct to understand that .wasm.js files should not be set as preload? Or is it any basis file that should not be set as preload? Or can developers go either way? @yaustar@yak32