Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2022.2.9f1
2023.2.0a4
Issue ID
UUM-28410
Regression
Yes
Assembly reference not detected when running Editor in batch mode after changing branches using git
Reproduction steps:
1. Open the attached “bug-assembly-reference-updated.zip” project
2. Close the project
3. Open the Terminal and navigate to the project’s folder
4. Run “git checkout master”
5. Run “{{/path/to/Editor -batchmode -quit -projectPath /path/to/project -executeMethod CommandLine.Build -logFile /path/to/project/build.log}}"
6. Open the Build.log file in the project’s folder
Expected result: "Assets/AssemblyOne/AssemblyOneTest.cs(5,9): error CS0103: The name ‘AssemblyTwoTest' does not exist in the current context" Error doesn’t exist in the Build.log file
Actual result: "Assets/AssemblyOne/AssemblyOneTest.cs(5,9): error CS0103: The name 'AssemblyTwoTest' does not exist in the current context" Error is present in the Build.log file
Reproducible with: 2022.2.9f1, 2023.2.0a4
Not reproducible with: 2020.3.45f1, 2021.3.20f1, 2023.1.0b6
Reproducible on: M1 macOS 13.1, Windows 10 (21H2)
Note: The issue is reproducible on both Intel and Apple Silicon Editors on M1 Mac
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Unfortunately this is as designed. Since the previous build is cached, it attempts to reuse it, fails to compile, then has a successful build. As the overall build passes with exit code 0, perhaps you can fix your CI system to check the exit code, instead of parsing the logs.
Resolution Note (2023.2.X):
Unfortunately this is as designed. Since the previous build is cached, it attempts to reuse it, fails to compile, then has a successful build. As the overall build passes with exit code 0, perhaps you can fix your CI system to check the exit code, instead of parsing the logs.