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
- The Scene view flickers when moving around if there are visible Hair Shaders
- The gradient ShaderGraph is inverted when using the Perceptual blend mode
- Particle System allocates large amounts of memory when it is very far away from the origin of the Scene
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
Add comment