Search Issue Tracker
Fixed in 2020.2.1b11
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a4
2022.1
2022.1.0a3
Issue ID
1355728
Regression
Yes
Profiler/Memory Profiler cannot be connected to Standalone build when Run in Background is disabled
How to reproduce:
1. Create an empty project
2. Select Edit/Project Settings/Player/Resolution and Presentation and disable Run in Background
3. Select Edit/Build Settings and enable Development build
4. Build and Run the project
5. Select Window/Analysis/Profiler and set your device as a target
Expected result: target is successfully set
Actual result: "Failed to connect to player ip" error appears or device does not appear on the targets list
Reproducible with: 2021.2.0a4, 2021.2.0b7, 2022.1.0a5
Not reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0a3
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2.1b11):
Fixed in: 2022.1.0a8
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b12