Regression from a1 to a8 (did not test a9-11).
WebGL Builds no longer run and throw the following error in browser;
A problem occurred while mounting RangeError
Code Optimization: Speed
Code Generation: Faster Runtime
Bug Report #1373141
Regression from a1 to a8 (did not test a9-11).
WebGL Builds no longer run and throw the following error in browser;
A problem occurred while mounting RangeError
Code Optimization: Speed
Code Generation: Faster Runtime
Bug Report #1373141
Nevermind.
Doing a “Clean Build” fixes the issue. Migration from a9 - a12 had cached data.
@LeonhardP , if I may.
Can Unity clean the WebGL / IL2CPP code cache between editor versions? Seems like it’s a recurrent issue due to the fact that the compiler backend keeps changing.
Another thread here:
An alternative workaround to Clean Build is to delete the BuildCache and Bee folders in Library prior to a build - maybe that’s the same as Clean Build. If the build won’t complete I delete Bee and just do both out of habit now if the build is crashing at startup in the browser. I get hit by this at random in 0a12. Other than that I’m quite happy with the alpha and looking forward to this being fixed.
My understanding is that it is indeed the same.
We currently have a PR in review that seeks to implement this behavior. Once it lands in 2022.1, the plan is to backport it to 2021.2 as well.