Search Issue Tracker
By Design
Votes
0
Found in
2022.2.1f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21125
Regression
Yes
WebGL build fails when building with a native library if “PlayerSettings.WebGL.emscriptenArgs” is set to “-s LLD_REPORT_UNDEFINED”
How to reproduce:
1. Open the attached user project “Native_Link_Repro-1416119.zip“
2. Build And Run (File>Build And Run)
Expected result: Player is built
Actual result: Error “Building Library/Bee/artifacts/WebGL/build/debug_WebGL_wasm/build.js failed with output“ in the Console
Reproducible with: 2022.2.0a16, 2022.2.1f1, 2023.1.0a23
Not reproducible with: 2021.3.15f1, 2022.1.24f1, 2022.2.0a15
Can’t test with: 2020.3.42f1 (Error “Failed process stderr log“ in the Console)
Reproduced on: macOS 13.0.1 (Intel)
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note:
This error is generated because the project contains a package which includes a pre-compiled plugin for Web built with the Emscripten toolchain. Unity 2022.2 was updated to use Emscripten 3.1.8 and therefore any pre-built plugin binaries also need to be built with the same version of Emscripten.
For the Draco package, this is tracked by https://github.com/atteneder/DracoUnity/issues/55