Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a6
Issue ID
1063709
Regression
Yes
[macOS] Unity fails to create C# project files resulting in autocomplete not working in UnityEngine/UnityEditor/etc. classes
Steps to reproduce:
1. Create a new project
2. Create a new script inside the project
3. Double-click the script to open it in VS for Mac
4. 2 errors are thrown and the C# project isn't generated (even though the script is opened correctly, the suggestions/autocomplete are not working for Unity classes):
NotSupportedException: Specified method is not supported.
SyntaxTree.VisualStudio.Unity.Bridge.ProjectSystem.UnitySolutionBuilder.ClassLibraryReference (System.String name) (at <70df2a6d49964eb58351ebd0338a7bed>:0)
Notes:
Trying to open C# project via Assets/Open C# project just throws the same error and doesn't open anything.
If you open a script on a project that has C# project files generated from an older Unity version, error is still thrown in console, but VS opens the project correctly and autocomplete works.
Reproduced with: 2018.3.0a4, 2018.3.0a6
Not reproduced with: 2018.3.0a3
Comments (3)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
jop_steel
May 29, 2019 19:52
Got this issue in 2019.1.4f1
NataliyaMilchenko
Apr 20, 2019 15:34
I got this issue in 2019.1.0f2
valmin
Mar 26, 2019 15:37
Has this issue in MacOS Unity 2018.3.0f2