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
- In Deferred rendering path, mixed lights don't render when enabling "Use Rendering Layers" in the Decal renderer feature
- [Windows] Special characters in file names are sorted to the end of the alphabet in the Project window
- Information box icons are not contained within the information box bounds in Render Pipeline Converter window
- Crash on UnityEngine.UI.RawImage:OnPopulateMesh when playing Raw Image Texture animation with Sprite keyframes
- 32bit floating point RenderTexture blending feature is not available for WebGPU
Add comment