Search Issue Tracker
Fixed in 1.0.4
Votes
0
Found in [Package]
1.0.3
Issue ID
1149924
Regression
No
[MacOS][VSCode] Visual Studio Code package throws error on opening scripts
Reproduction steps:
1. Open "VSCodeWrong.zip" project
2. Make sure that Visual Studio (Community) or Visual Studio Code is selected as the External Script Editor
3. Double Click the "NewBehaviourScript"
4. Notice Errors in the Console
Expected Result: No errors
Reproduced with: 2019.3.0a1, 2019.2.0a14, 2019.2.0a12
Did not reproduce on: 2019.2.0a11, 2019.1.1f1 (Only implemented from 2019.2.0a12)
Note:
Does not reproduce on Windows
Tested on MacOS 10.14.4
Errors:
Visual Studio Code:
"Exception thrown while invoking [OnOpenAssetAttribute] method 'Unity.CodeEditor.CodeEditor:OnOpenAsset (int,int,int)' : Win32Exception: Cannot find the specified file"
"Win32Exception: Cannot find the specified file"
Visual Studio Community:
"Exception thrown while invoking [OnOpenAssetAttribute] method 'Unity.CodeEditor.CodeEditor:OnOpenAsset (int,int,int)' : Win32Exception"
"Win32Exception: ApplicationName='/Users/qa/Desktop/case_1149924-VSCodeWrong/Library/PackageCache/com.unity.ide.visualstudio@1.0.4/Editor/COMIntegration/Debug/COMIntegration.exe',"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph Particles render black when using Baked GI in URP Unlit Shader Graph
- Crash on Unity::Joint::SetJointLocalActorFrames when changing connectedBody on a ConfigurableJoint
- WebGL player crashes on RuntimeError when using the Disk LTO code optimization
- All Animators previous animations are activated while transitioning when a second split-off transition overrides the first split-off transition
- Warning that external text editor path does not exist when manually selecting specific code editors such as VSCodium or TextEditor
Add comment