Search Issue Tracker
Fixed
Fixed in 1.1.33
Votes
0
Found in [Package]
1.1.29
Issue ID
DSTR-394
Regression
No
Unity test-framework does not set BuildTargetGroup when debugger is attached
How to reproduce:
1. Open project "UTFNotSettingBuildTargetGroup.zip"
2. Open TestPlayerBuildModifier in the script editor (Assets>Editor>TestPlayerBuildModifier)
3. Attach to Unity
4. Make a breakpoint in the 14th line
5. In the Unity Editor open the Test Runner Window (Window>General>Test Runner)
6. Select PlayMode
7. Press "Run All Tests"
8. Go to the script editor and open playerOptions (Locals tab for Visual Studio)
9. Open it and look at the "targetGroup"
Expected result: targetGroup should be set to "Standalone"
Actual result: targetGroup is set to "Unknown"
Reproducible with: 1.1.29 (2019.4.30f1, 2020.3.19f1, 2021.1.21f1, 2021.2.0b13, 2022.1.0a11)
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note (fix version 1.1.33):
Fixed in: 1.1.33 (2019.4.0f1)