Search Issue Tracker
Active
Votes
0
Found in [Package]
1.1.9
Issue ID
DSTR-14
Regression
No
Debug.Log() Context not highlighted when pressed after printing in Test Runner's EditMode
Repro steps:
1. Open attached "case-1170589.zip"
2. In the Editor, go to "Window" > "General" > "Test Runner" > "EditMode" > "Run All"
3. In Hierarchy, expand "Sample Scene" so that you could see the elements
4. In Console, consecutively click on both Debug.Log and Debug.LogError produced messages
Expected results: in Hierarchy, "GameObject (1)" gets highlighted right after clicking on the first error message
Actual results: "GameObject (1)" is not highlighted
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Add comment