Search Issue Tracker
Fixed
Fixed in 1.2.X
Votes
0
Found in [Package]
1.2.X
Issue ID
ULOG-28
Regression
Yes
IDE does not open when double-clicking on a log message in the Console window
How to reproduce:
1. Open the “LoggingIDEIssue“ project
2. Open the “SampleScene”
3. Enter Play Mode
4. In the Console window observe the newly logged message that includes “| INFO | Hello”
5. Double-click the newly logged message that includes “| INFO | Hello”
Expected result: IDE opens on the exact line where “log.info” is called
Actual result: IDE does not open on the exact line where “log.info ” is called
When using the logging package 1.2 and a log sink, double clicking the entry in the console results in an error popup
When using the logging package 1.0 and a log sink, double clicking the entry in the console results the IDE opening to the sink script in the logging package rather than the point where Log.Info is called.
Reproduced with: 1.1.0-exp.1, 1.2.0-pre.4 (2022.3.15f1, 2023.2.4f1, 2023.3.0a18)
Not reproduced with: 1.0.16 (2022.3.15f1, 2023.2.4f1, 2023.3.0a18)
Could not test with: 1.0.16-1.2.0-pre.4 (2021.3.33f1) (Package not supported)
Reproduced on: macOS 14.0 (by reporter), macOS 12.6.1 (M1), Windows 11
Not reproduced on: No other environment tested
Notes:
1. On macOS 12.6.1 from the FAV and upwards the IDE only opens the project select menu
2. On Windows 11 from the FAV and upwards the IDE does not open at all
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
Resolution Note (fix version 1.2.X):
As reported, the behavior is as designed. The debug log sink (configured with WriteTo.UnityDebugLog) is meant as a test logger that just forwards messages directly to Unity.DebugLog and it's expected that some information will be lost that way. You probably want to use WriteTo.UnityEditorConsole instead which is much more performant and supports features like double-clicking log entries to be brought to that line in your IDE. Although at the moment this specific feature is broken on that sink too, although there is a fix for that on the way, probably landing in the next release of the package (which would be 1.2.0-pre.7).