Search Issue Tracker
Fixed in 2021.3.26f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Add comment