Search Issue Tracker
Active
Votes
0
Found in
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1319234
Regression
Yes
[Big Sur] Profiler cannot be connected to build when using Autoconnect Profiler option in Build Settings
Steps to reproduce:
1. Create a new project
2. Open Profiler window
3. Open Build Settings
4. Check "Development Build" and "Autoconnect Profiler" options
5. Build and run the app
Expected results: Profiler is automatically connected to the running build
Actual results: "Failed to connect to player ip" error is produced
Reproducible with: 2019.3.0f5, 2020.3.1f1, 2021.1.0f1, 2021.2.0a10
Not reproducible with: 2018.4.33f1, 2019.3.0f6, 2019.3.15f1, 2019.4.0f1, 2019.4.22f1
Notes:
- When trying to connect to the same build manually by selecting it in Profiler, the same error is produced
- Issue also reproduces when opening Standalone Profiler window
- Not reproducible on Catalina (10.15.7)
- Reproducible with Big Sur (11.1, 11.2)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment