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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment