Search Issue Tracker
Found in [Package]
[VSCode] OmniSharp project reference warnings are thrown in VSCode console when using VSCode 1.1.4
How to reproduce:
1. Create a new Unity project
2. Make sure that your External Code Editor is set to VSCode and VSCode package version is 1.1.4
3. Click on Assets > Open C# Project
4. Once the VSCode window is open, go to the Output tab and inspect OmniSharp Logs
Expected results: No warnings regarding the referenced project being missed are thrown
Actual results: Many "Expected project reference Unity.TextMeshPro.Editor.csproj to be already loaded for project Assembly-CSharp" warnings are thrown
Reproducible with: 2019.2.19f1, 2019.3.0f6, 2020.1.0a20
Reproducible with package version: 1.1.4
Not reproducible with package version: 1.1.3
1. Downgrading VSCode package to version 1.1.3 fixes the issue.
2. Reproduced on Windows and MacOS.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Jan 30, 2020 16:05
Confirmed on Unity Version 2019.3.0f6 on OS X.
As SergioCarneiro said:
1.- Downgrading to 1.1.3
2.- Close Unity
3.- Removing C# Project files (*.csproj)
4.- Reopening Unity fixes it.
Jan 30, 2020 15:06
I have the same issue (Unity 2019.3.0f6 - Windows).
Downgrading the Visual Studio Code Editor package to 1.1.3 did not fix the issue.
Example of warning - this appears hundreds of times for each package.
Expected project reference c:\Users\ProjectLocation\com.unity.multiplayer-hlapi.Runtime.csproj to be already loaded for project Assembly-CSharp
Jan 30, 2020 05:49
Confirmed with Unity 2019.3.0f6 on OS X.
Downgrading to 1.1.3 worked.
The issue came up after creating a new project and importing script files to it from another project.
After opening VSCode, OmniSharp started complaining the following among many others like it:
The referenced project 'Unity.VSCode.Editor.csproj' does not exist.
The referenced project 'UnityEngine.UI.csproj' does not exist.
Jan 29, 2020 22:50
Can confirm Unity 2019.3.0f6 on Windows 10. Issue arose after upgrading a project from 2019.2.17 to 2019.3.0f6.
Downgrade to v1.1.3 fixed the issue for us.
Jan 28, 2020 23:22
I have the same issue. Can't confirm those exact steps reproduce the error, but downgrading surely fixed it.
Steps to Fix:
1. Downgrade to v1.1.3
2. Close Unity
3. Remove all C# project files
4. Open Unity
Jan 28, 2020 20:22
Can confirm with Unity 2019.3.0f5 on OS X.
Also can confirm 1.1.3 downgrade fixes issue.