Search Issue Tracker
Fixed in 2020.3.43f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
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
- 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
Add comment