Search Issue Tracker
Fixed in 1.1.2
Votes
2
Found in [Package]
1.0.2
Issue ID
1171319
Regression
No
[Mac] Double clicking on the Error entry in the Unity Editor console does not open the line causing the error when using VSCode
How to reproduce:
1. Open the attached "VSCode_issue" project
2. Make sure that default text editor is VS Code
3. Double-click on a script error entry in the Editor Console
Expected result: VSCode will show the exact line where the error has occurred
Actual result: VSCode shows it's welcome screen instead of the script file
Reproducible with: 2019.2.0f1 (package ver. 1.0.2, 1.0.3, 1.0.7), 2019.3.0a11 (package ver. 1.0.2, 1.0.3, 1.0.7)
Not reproducible with: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0a11
Additional notes:
1. This issue does not reproduce on Windows since version 2019.3.0a1, however, it continues to reproduce on Mac
2. 2019.2.0a12 is the version where VSCode Editor package has appeared in the Package Manager
3. The issue may also reproduce differently: VSCode can open the script file, but still won't show the exact error line
Solved in package version 1.1.2.
-
azixMcAze
Aug 23, 2019 07:07
Double clicking on a script in the project window on clicking on Open C# Project will also open VSCode without opening the file or the project.
It is reproducible with package 1.1.0
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
- 3D Sample Scene (HDRP) template tutorial Welcome Dialog pop-up doesn't appear on project creation
- [Profiler] The Addressable Asset Module module outputs an ArgumentException when asset GUIDs produce a hash collision with Addressables
- Huge amounts of tests have a start delay when pressing "Run All" in the Test Runner
- Blackboard: Double borders around the tooltip
- [WebGL]VideoPlayer Rendering stops when setting FilterMode of a texture downloaded with UnityWebRequestTexture.GetTexture()
Resolution Note (fix version 1.1.2):
Solved in package version 1.1.2