Search Issue Tracker
Fixed
Fixed in 2020.3.43f1, 2021.3.13f1, 2022.2.0a6
Votes
1
Found in
2020.3.23f1
2021.2.4f1
2022.1.0a16
Issue ID
UUM-7955
Regression
No
The Player not listed in the Unity Instance window in VS when using BuildOptions.AllowDebugging and BuildOptions.ConnectToHost
How to reproduce:
1. Open the attached project "Repro.zip"
2. Build And Run with MyTools>Windows Build With Postprocess
3. Open Visual Studio
4. Open Debug>Attach Unity Debugger
Expected results: The Player is listed in the Unity Instance window
Actual results: The Player is not listed in the Unity Instance window
Reproducible with: 2019.4.33f1, 2020.3.23f1, 2021.2.4f1, 2022.1.0a16
Notes: Commenting out 'options |= BuildOptions.ConnectToHost;' at line 15 fixes the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment