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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 1.1.33):
Fixed in: 1.1.33 (2019.4.0f1)