Search Issue Tracker
Fixed
Fixed in 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a18
Votes
9
Found in
2023.1.0a6
Issue ID
UUM-1156
Regression
No
Give error when building WebGL on CentOS7
How to reproduce:
1. Open attached project
2. Change platform to WebGL
3. Build and run
Console is filled with errors:
Building Library/Bee/artifacts/WebGL/GameAssembly/master_WebGL_wasm/bgiy_gistration.o failed with output:
Traceback (most recent call last):
File "/home/justas/Unity/Hub/Editor/2021.2.0b11/Editor/Data/PlaybackEngines/WebGLSupport/BuildTools/Emscripten/emscripten/emcc.py", line 116, in <module>
returncode = run(cmd)
File "/home/justas/Unity/Hub/Editor/2021.2.0b11/Editor/Data/PlaybackEngines/WebGLSupport/BuildTools/Emscripten/emscripten/emcc.py", line 70, in run
cmd = cmd\[:2] + \['@' + create_response_file(cmd\[2:])]
File "/home/justas/Unity/Hub/Editor/2021.2.0b11/Editor/Data/PlaybackEngines/WebGLSupport/BuildTools/Emscripten/emscripten/emcc.py", line 61, in create_response_file
with os.fdopen(response_fd, 'w', encoding='utf-8' if WINDOWS else None) as f:
TypeError: fdopen() takes no keyword arguments
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /home/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)
and finishes with:
BuildFailedException: Incremental Player build failed\!
UnityEditor.Modules.BeeBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at /home/bokken/buildslave/unity/build/Editor/Mono/Modules/BeeBuildPostprocessor.cs:551)
UnityEditor.WebGL.WebGlBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at /Users/bokken/buildslave/unity/build/PlatformDependent/WebGL/Extensions/Unity.WebGL.extensions/BuildPostprocessor.cs:157)
UnityEditor.Modules.DefaultBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args, UnityEditor.BuildProperties& outProperties) (at /home/bokken/buildslave/unity/build/Editor/Mono/Modules/DefaultBuildPostprocessor.cs:28)
UnityEditor.PostprocessBuildPlayer.Postprocess (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget target, System.Int32 subtarget, System.String installPath, System.String companyName, System.String productName, System.Int32 width, System.Int32 height, UnityEditor.BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry, UnityEditor.Build.Reporting.BuildReport report) (at /home/bokken/buildslave/unity/build/Editor/Mono/BuildPipeline/PostprocessBuildPlayer.cs:370)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&) (at /home/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)
Reproduced with: 2021.2, 2022.1
-
ZINKYGAMES
Dec 30, 2021 13:31
I have same issue for Android build. Using Unity 2021.2.7f1.
-
Abed_Kadah
Dec 20, 2021 09:03
Same issue here (same error), I hope we will get a fix very quick.
-
mgazillion
Dec 19, 2021 22:06
Same issue.
I'm not sure why it's happening because it's just stating the location of the errors, not telling me why they're coming up. -
Okeir
Nov 26, 2021 04:46
Having a similar issue, in my case it is complaining about a missing 'Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle'. It works well when compiled for desktop platform. I'm using MacOS - M1 Chip.
Did you manage to resolve it?
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
- Prefab's scripts are constantly reloaded when trying to enter multiple digits or characters into public fields on custom scripts consecutively
- [Linux] Progress modal window stays on top of every other window and cannot be moved
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
- Sprite Atlas remains loaded in memory after scene change or unloading assets
Resolution Note (fix version 2023.1.0a18):
With Unity 2021.2 and later we only support WebGL builds with the Linux Editor on Linux distributions which include glibc 2.27 or later (i.e. Ubuntu 18+)
Resolution Note (fix version 2022.2.0b15):
Fixed in 2022.2.0b15
Resolution Note (fix version 2022.1.23f1):
Fixed in 2022.1.23f1
Resolution Note (fix version 2021.3.14f1):
Fixed in 2021.3.14f1