Search Issue Tracker

Fixed in 1.1.2

Votes

37

Found in [Package]

1.0.7

Issue ID

1173165

Regression

Yes

[Mac] A new script is not being opened as a different tab when using VSCode

Package: VS Code

-

How to reproduce:
1. Create a new Unity Project
2. Make sure VSCode is set as a default text editor
3. Create two scripts
4. Open the first script, then open the second one

Expected results: Both scripts are opened in VSCode in separate tabs
Actual results: Only first opened script is shown in VSCode

Reproducible with: 2019.2.0a12, 2019.2.0f1, 2019.3.0a11 (package ver 1.0.7)
Not reproducible with: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0a11

Additional notes:
1. It was tested on OS X 10.14.2 and 10.14.4. The issue reproduces on 10.14.2. On 10.14.4 VSCode opens it's welcome screen only
2. Package versions 1.0.2 and 1.0.3 throw Win32Exceptions on a Mac, however, the issue does not reproduce

Resolved in package version 1.1.2
Log in to vote on this issue

Comments (12)

  1. juanfornos

    Sep 11, 2019 00:14

    Never mind, I updated to Unity 2019.2.4f1 and the version 1.1.2 is now available in the package manager. Thanks!

  2. juanfornos

    Sep 10, 2019 16:04

    AMROC: Thanks for the info! Which version of Unity are you running? The version 1.1.2 isn't available to me on the Package Manager (Unity 2019.2.0f1) and doesn't appear on the package changelog yet. That's why I thought it wasn't available to the public yet.

  3. amroc

    Sep 09, 2019 16:24

    JUANFORNOS & MUCKEL: 1.1.2 is available for me from the package manager, I updated it on the 6th of September.

  4. juanfornos

    Sep 09, 2019 14:59

    MUCKEL: It seems the version 1.1.2 isn't available to the public yet: https://docs.unity3d.com/Packages/com.unity.ide.vscode@1.0/changelog/CHANGELOG.html

    Meanwhile you can workaround this by running this script after each time you open Unity (set PROJECT_PATH with your project's path)

    sed -i '' 's/\$\"\\\"{GetDefaultApp}/$"-n \\\"{GetDefaultApp}/g' ${PROJECT_PATH}/Library/PackageCache/com.unity.ide.vscode@1.0.7/Editor/VSCodeScriptEditor.cs

  5. Muckel

    Sep 06, 2019 14:35

    bug is still present!!!
    Unity what are you doing?
    where is the QA and bug testing...

  6. jirimotejlek

    Aug 29, 2019 16:42

    Basically, Visual Studio Code doesn't work with Unity on macOS.
    Since editing scripts seems like a quite vital functionality for any IDE, how does this issue still exist after three unity releases is a mystery to me.

  7. Conferno

    Aug 27, 2019 12:58

    Yes, this is annoying. I have this bug too

  8. antpaw

    Aug 09, 2019 09:38

    as pointed out here https://forum.unity.com/threads/cant-get-vscode-to-work-properly-with-unity.538224/

    this seams to fix it : Arguments = $"-n \"{GetDefaultApp}\" --args {arguments}",

  9. tboebb

    Aug 09, 2019 07:32

    I can confirm it as well.
    This is very annoying.

  10. unity_2L-MlLDX1uzHPg

    Aug 08, 2019 07:19

    Can confirm, this happens since I updated Unity to 2019.2.

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.

Latest issues

See all new issues