Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2018.4.0f1
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1193777
Regression
Yes
Profiler stucks with Autoconnected Player option and can't be switched back to Editor when AndroidPlayer is selected
How to reproduce:
1. Create a new project
2. Open Window -> Analysis -> Profiler
3. Enter Play Mode
4. Select AndroidPlayer(samsung_SM-G977U) in the Attach to Player dropdown
5. Select Editor in the Attach To Player dropdown
Expected result: Editor option is selected and Profiler continues working
Actual result: Editor option can't be selected and Profiler is stuck with Autoconnected Player option
Reproducible with: 2018.4.0f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b8, 2020.1.0a9
Not reproducible with: 2017.4.33f1
Notes:
- Profiling can't be switched back to Playmode from Autoconnected Player too
- When it's switched to another Player such as AndroidPlayer(Huawei_LYA-L29) Profiler continues working as usual
- When AndroidPlayer(samsung_SM-G977U) is selected error is thrown: Socket: connect failed, error: A non-blocking socket operation could not be completed immediately. (10035)
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
- Memory access out of bounds error is thrown when launching Web builds with C/C++ Multithreading enabled
- Warning text is not aligned in Project Settings > In-App Purchasing tab
- "In-App Purchases" name mismatch in Project Settings window and Package Manager Window
- An opaque Texture has semi-transparent edges when packed in a Sprite Atlas
- Player builds with android:installLocation="0" when Install Location is set to "Automatic"
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a18, backported to 2019.3.0f5, 2019.2.18f1, 2018.4.17f1