Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2019.1.0a5
2019.2.17f1
Issue ID
1210338
Regression
Yes
[WebGL] Build fails with Developement and AllowDebugging options
Steps to reproduce:
1. Open original users project "AutoBuild.zip"
2. In top menu press Build -> Dev_AllowDebugging
Expected result: Build succeeds as building "Build -> Dev"
Actual result: Build fails with errors in the console (errors in edit)
Reproduced in: 2019.1.0a5, 2019.2.18f1, 2019.3.0f4, 2020.1.0.a19
Not reproduced in: 2017.4.36f1, 2018.4.15f1, 2019.1.0a4
Note: this is treated as a cosmetic issue because managed code debugging is not supported on WebGL.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Considering that script debugging is not supported on WebGL, the BuildOptions.AllowDebugging option will be ignored on WebGL, and a warning message will be shown in the console when this option is enabled.
Resolution Note (fix version 2019.4):
verified
Version 2019.4.3f1 (f880dceab6fe)