Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.2
1.1.3
1.1.4
Issue ID
VSC-7
Regression
Yes
[OSX]Non-existent scripts are attempted to be opened when double-clicking on editor warnings and messages
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager window
3. Remove any installed package
4. In the Menu bar select Help > Reset Packages to defaults
5. Once the packages are reset double-click on the "Packages were changed." message in the Console window
Expected result: no instance of a code editor is opened
Actual result: a code editor opens with different behaviour on different Code Editors
Reproducible with: 2019.1.0a12, 2019.1.14f1, 2019.2.8f1, 2019.3.0b6, 2020.1.0a7
Not reproducible with: 2017.4.33f1, 2018.4.10f1, 2019.1.0a11
Reproducible with package versions: 1.0.2, 1.1.3
Notes:
Could not reproduce on Windows
Tested with Visual Studio Code and Visual Studio
Visual Studio opens a blank window/solution
Visual Studio Code opens an empty script in older Unity versions, throws a "Path does not exist" pop-up in newer versions
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Couldn't reproduce in
Version: 2020.2.0a21.2837
Revision: trunk 3e0d5f775006
Tried on both Mac 10.13.6 and Win10