Search Issue Tracker
Fixed
Fixed in 2021.3.26f1, 2022.2.21f1, 2023.1.0b18, 2023.2.0a16
Votes
1
Found in
2021.3.24f1
2022.1.24f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-35390
Regression
No
Command line build - BuildProgram exited with code -2147024809 when AllowDebugging flag passed to build options
1. What happened
Command line builds fails with code -2147024809 when building to Windows Standalone with AllowDebugging flag passed into build player options.
2. How can we reproduce it using the example you attached
No example attached. Please follow thread at https://support.unity.com/hc/en-us/requests/1536166
Should be reproducible by performing Windows Standalone build via the command line. Executed method should pass in the AllowDebugging flag to BuildOptions.BuildPlayerOptions. Using EditorUserBuildSettings.allowDebugging has no effect.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
Add comment