Search Issue Tracker

Fixed

Votes

50

Found in [Package]

1.1.4

Issue ID

VSC-9

Regression

Yes

[VSCode] OmniSharp project reference warnings are thrown in VSCode console when using VSCode 1.1.4

Package: VS Code

-

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

Notes:
1. Downgrading VSCode package to version 1.1.3 fixes the issue.
2. Reproduced on Windows and MacOS.

Comments (27)

  1. Kruczek

    Mar 22, 2020 15:04

    Reproduced on 2019.3.6f1, both packages 1.1.4 and 1.1.3 have the same issue.

  2. adecamillo

    Mar 09, 2020 15:25

    Reproduced with Unity 2019.3.0f6, package version 1.1.4, Windows 10

  3. caglarenes

    Mar 09, 2020 12:17

    Reproducible with 2019.3.4f1 on Windows 10 and OSX. Downgrading to 1.1.3 didn't work on both operating systems.

  4. NGC6543

    Feb 27, 2020 06:40

    Downgrading the package version to v1.1.3 doesn't solved the issue on Unity2019.3.2f1.

  5. Albob

    Feb 18, 2020 14:32

    Reproducible on 2019.2.15f1 with package version 1.1.4 on macOS Catalina 10.15.2

  6. bdrelling

    Feb 18, 2020 04:14

    Reproducible on 2019.3.0f6 and 2019.3.1f1 with package version 1.1.4 on macOS Catalina 10.15.2.

  7. ROBYER1

    Feb 17, 2020 08:39

    Reproduced on 2020.1.0a23 and it is very annoying as the package auto updates to the latest verified on these engine versions!

  8. Fethbita

    Feb 16, 2020 16:48

    Reproducible with 2019.3.1f1 and package version 1.1.4 on Windows 10.
    Reproducible with 2019.3.0f5 and package version 1.1.4 on Arch Linux.

  9. Odiobill

    Feb 09, 2020 10:11

    I'm also having the same issue since upgrading to 2019.3.0f6.

    Downgrading to 1.1.3 seems to fix the issue, but on the other hand, it makes the situation even worst since IntelliSense doesn't seem to work: no files are actually added to the workspace until you start changing something, and it can't autocomplete from other references.

    Upgrading again to 1.1.4 fixes the IntelliSense issue but brings back the hundreds of errors in the console and VSCode thinks that some files are broken, being unable to solve those references, while everything works in Unity.

  10. Alieldin

    Feb 03, 2020 21:36

    Confirmed, downgrading to 1.1.3 fixes the issue on Unity 2019.3.0f6, tested on Windows 10.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.