Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.22f1
2020.3
2021.1
2021.2
Issue ID
1322579
Regression
No
[OSX] Symbol definitions are not detected (greyed out) in code editor when a Script is inside an UPM package installed via git
How to reproduce:
1. Open the attached project
2. In the Project Window, navigate to Packages->Example Package->Scripts
3. Open the "ExampleUsage.cs" Script in a code editor
4. In the code editor, inspect the branching of the symbol define
Expected result: Unity symbol definitions are detected and the active code is highlighted
Actual result: Unity symbol definitions are not detected and the active code is greyed out
Reproducible with: 2019.4.24f1, 2020.3.3f1, 2021.1.2f1, 2021.2.0a12
Couldn't test with: 2018.4.33f1 (Assemblies throw errors)
Tested with:
- Rider (2020.3.2, Build #RD-203.6682.21)
- Visual Studio (8.6.5)
Note: The code is executed correctly but the defines are shown incorrectly
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
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
- Rendering Debugger throws a warning and renders the Scene view in solid black when material debug tools and Path Tracing are used
- User gets "NullReferenceException: Object reference not set to an instance of an object" error in the Console during the search in the "Select Scene" window
Resolution Note:
This is actually by design: by default git packages don't have their project generation turned on, and so the code editor does not know which defines are enabled.
This can be changed in editor preferences: In editor preferences, check "git packages" in "generate .csproj file for" and regenerate projects. This fixes the issue.