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
- [Xcode] "InfoPlist (English)" is required when "InfoPlist (English (United States))" already exists
- [tvOS] Crash when closing the On Screen Keyboard with tvOS version <15.0
- Temporal Anti-aliasing (TAA) produces severe artifacting when quality set to Very High
- [iOS] Player crashes when using “WebCamTexture” on specific iOS devices
- [Linux][IL2CPP] Player crash call stack is not displayed when the build is run with "-batchmode -nographics" arguments
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0b4