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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment