Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.2.0a4
Issue ID
1312439
Regression
No
[Profiler] When 2 devices are connected to a profiler, message is cutoff by other connection and uninformative error appears
How to reproduce:
1. Create a new project
2. Open Profiler
3. Switch platform to Android
4. Connect two devices via USB
5. In Build settings enable Development and Autoconnect profiler
6. Build and run on both devices
7. App starts, profiler pauses
Actual result: after some time you get an error because message was cutoff by other connection, but it is not informative enough
"The message body receive resulted in error. Discarding message."
Expected result: Error message could contain information about connection x device
Reproducible: 2021.2.0a4
Not reproducible: 2020.2.3f1 <- I cannot get this error message in this version, because profiler behaviour was different (previously devices'd get a faked multicast connection) and now profiler is being updated.
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
Add comment