Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.4
2019.4
2019.4.1f1
2020.1
2020.2.0a1
Issue ID
1259355
Regression
No
Autoconnect Profiler doesn't set the device target to profile automatically
Reproduction steps:
1. Create a new project, set the Build Platform to Android
2. In the Build Settings window turn on the Development Build and Autoconnect Profiler
3. Build and Run to an Android Device
Expected result: After deploying to an Android device the Profiler window shows up already connected to the device, showing the profiling data
Actual result: The Profiler window shows up empty, need to manually set the target device to profile from
Reproduces on: 2018.4.24f1, 2019.4.5f1, 2020.1.0f1, 2020.2.0a12
Not reproducible on: 2020.2.0a13
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2020.2.X):
fixed in: 2020.2.0a13