Search Issue Tracker
Active
Under Consideration for 6000.5.X, 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-135042
Regression
No
Build fails with a warning when running Unity Editor’s csc.dll manually using dotnet command
How to reproduce:
1. Extract and open the attached “NetcodeRepro.zip“ project
2. Navigate to the project folder using the Terminal
3. Execute the following command:
”dotnet /Applications/Unity/Hub/Editor/<Editor Version>/Unity.app/Contents/Resources/Scripting/DotNetSdkRoslyn/csc.dll @Library/Bee/artifacts/200b0aEDbg.dag/TestAssembly.rsp”
4. Observe the Terminal output
Actual result: A warning message appears, and the generation fails
Expected result: The command runs without warnings, and the generation succeeds
Reproducible with: 2023.2.0b1, 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Could not test with: Older versions, because they produce various package errors
Reproducible on: macOS 26.2 (M1 Silicon)
Could not reproduce on: No other environment tested
Note: to find the correct “csc.dll“ file location for any given Editor version, use the command “find "/Applications/Unity/Hub/Editor/<Editor Version>/Unity.app/Contents" -iname csc.dll“
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
Add comment