Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.4
2020.1
2020.2
2021.1
2021.1.0a7
Issue ID
1297201
Regression
No
[Profiler] "Failed to connect to player" error is thrown when trying to connect to a closed player
How to reproduce:
1. Create a new project
2. Open the Build Settings (File->Build Settings...)
3. In the Build Settings window enable "Development Build" and "Autoconnect Profiler" options
4. Build And Run the project
5. In the Profiler window switch to Editor and change Profiling Target to Editor
6. Close the Build
7. In the Profiler window switch the Profiling Target to Player
Expected results: No errors are thrown in the Console
Actual results: The "Failed to connect to player IP" error is thrown in the Console
Reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a9
Notes:
- Closing the Build without switching the Profiling Target does not produce the error
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0b4