Search Issue Tracker
Fixed in 2021.2.1b4
Votes
0
Found in
2021.2
2021.2.0a17
Issue ID
1339420
Regression
No
Errors are thrown when building project for WebGL where project is on a different drive to Unity Editor
How to reproduce:
1. Open a new Unity project
2. Build for WebGL
Expected result: Build is successful
Actual result: Multiple errors are thrown in the Console log and Build stops
Reproducible with: 2021.2.0a17, 2021.2.0a20
Could not test with: 2018.4.34f1, 2019.4.27f1, 2020.3.12f1, 2021.1.10f1 (Does not have the incremental builder)
Note:
- Not reproducible on Mac, while it reproduces on Windows
Comments (4)
-
TheNerdyBoy
Nov 17, 2022 01:54
Yep, needs to be on the same drive. That is what made it work for me.
-
DamianoP
Jun 06, 2022 00:21
2021.3.4f1 the problem is still here
-
orangetech
Apr 21, 2022 15:45
2021.3.0f1c1(LTS) still have this problem
-
problemecium
Nov 11, 2021 05:46
NOT resolved in 2021.2.1f1 as of today.
1. Create a new Unity project on a drive other than the one containing the Unity Editor installation
2. Switch platform to WebGL
3. I set "Code Optimization" to "Size" and "IL2CPP Code Generation" to "Faster (smaller) builds" but this doesn't seem likely to be the issue
4. Build the project
Expected: built WebGL player
Actual: WebGL build fails. A series of errors appears in the Console, including:
"C:/Program Files/Unity/Editor/Data/PlaybackEngines/WebGLSupport/BuildTools/Emscripten/llvm\llvm-ar.exe: error: Library/Bee/artifacts/WebGL/GameAssembly./master_WebGL_wasm/GameAssembly..bc: function not supported"
Workaround: move the project to the same drive as the Editor (in this example, the C drive); WebGL build now completes successfully.
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 2021.2.1b4):
Fixed in 2021.2.0b4