Search Issue Tracker
Fixed in 2020.2
Fixed in 2018.4, 2019.3, 2020.1
Votes
0
Found in
2017.4.35f1
2019.3.0f6
Issue ID
1224614
Regression
No
Console Logs from built Players are not received by an attached Editor until Console Connection drop-down is clicked
How to reproduce:
1. Open the attached project in the Unity Editor
2. Do NOT touch the Console window's Connection drop-down until later (step 6)
3. Build and run a development player with auto connect profiler
4. once build and connected, validate that the connection is established (profiler receives data)
4.b) if no connection was established yet, establish it via the profiler Window's connection drop-down
5. check Console window, see that no logs are received
Expected: Logs emitted in the Player are received in the Console Window of the attached Editor.
Actual: Logs emitted in the Player are NOT received in the Console Window of the attached Editor.
6. Click on Console Window's connection drop-down and outside of it
7. See logs being received now
Reproduces with 2019.3.0f6, 2017.4.35f1
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
- Nodes in the Vertex block are deleted when the edge connected to the Node is deleted
- Changes to instanced detail mesh material don't immediately apply
- Scroll bar scrolls less in the Package Manager packages than elsewhere when pressing on the empty scroll bar area to scroll
- Undo.RegisterCreatedObjectUndo dirties the scene, but no actual changes to Scene are made
- [Profiler] Scrubbing through filtered frames or sorting their data replaces the displayed data with duplicated data entries
Resolution Note (fix version 2019.3):
Fixed in 2019.3.9f1