Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.0a11
Issue ID
UUM-32876
Regression
Yes
Editor fails to Build when building for WebGL Platform
How to reproduce:
1. Open the "WebGL_Build_Bug" project
2. Open the “SampleScene”
3. Make sure to switch Build to “WebGL” (Edit > Build Settings)
4. Build And Run
5. In Editor, observe errors logged to the Console
Expected result: the WebGL Player is built successfully
Actual result: the WebGL Player is not built, and the Editor logs errors to the Console
Reproduced with: 2021.2.0a8-2021.2.0a11
Not reproduced with: 2020.3.47f1, 2021.2.0a7, 2021.3.22f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a10
Fixed in: 2021.2.0a12
Reproduced on: Windows 11
Editor Build error logs:
Log #1:
{noformat}Build completed with a result of 'Failed' in 7 seconds (6782 ms)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun (){noformat}
Log #2:
{noformat}UnityEditor.BuildPlayerWindow+BuildMethodException: 2 errors
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (UnityEditor.BuildPlayerOptions options) [0x002ca] in <40e0f89d03e04ba1acbe14c6bc2cc603>:0
at UnityEditor.BuildPlayerWindow.CallBuildMethods (System.Boolean askForBuildLocation, UnityEditor.BuildOptions defaultBuildOptions) [0x00080] in <40e0f89d03e04ba1acbe14c6bc2cc603>:0
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun (){noformat}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Scaled Backgrounds List and dropdown text are enabled while Scaled Backgrounds field is disabled in IMGUI Debugger window
- Editor crashes when large value is entered in Scaled Backgrounds field of IMGUI Debugger window
- "Custom Function" Node "Input" type changes do not immediately show mistmatch errors when set to an incompatible type in Shader Graph
- My Assets list is populated with Asset Packages when setting how many Packages to display before clicking the Load button
- Hub shows 6.0 as Latest LTS when opening a project after deleting its 6.3 Editor version
Resolution Note:
This appears to be a transient issue between Unity releases (a8-a11 of 2021.2.0) and is noted as fixed in 2021.2.0a12. As such, the resolution is to upgrade to a suitable later version of Unity 2021.2.