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.
Comments (1)
-
hammad2
Dec 10, 2020 11:10
When your website or blog goes live for the first time, it is exciting. That is until you realize no one but you and your. ντετεκτιβ
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
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)