Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2018.4.12f1
2019.2
2019.3
2020.1
Issue ID
1203250
Regression
No
Using "EditorUserBuildSettings.SwitchActiveBuildTarget" in code does not update the "selectedBuildTarget"
Reproduction steps:
1. Open "Test.zip" project
2. "Tools" -> "SwitchMe"
3. Notice the Console Output
4. "Tools" -> "SwitchMe"
5. Notice the Console Output
Expected Result: Using "EditorUserBuildSettings.SwitchActiveBuildTarget" in code updates the "selectedBuildTarget"
Actual Result: Using "EditorUserBuildSettings.SwitchActiveBuildTarget" in code does not update the "selectedBuildTarget"
Reproduced with: 2020.1.0a17, 2019.3.0f4, 2019.2.17f1, 2018.4.15f1, 2017.4.35f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
"selectedBuildTargetGroup" controls the Build Player Window selection only and is controlled independently from "SwitchActiveBuildTarget". You can use this property directly to set the selected group if desired.