Search Issue Tracker
Won't Fix
Under Consideration for 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2022.3.9f1
2023.1.12f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-48987
Regression
No
Internal build system error when trying to reference the main Assembly-CSharp
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Observe the Console window
Expected result: No console errors
Actual result: Console error “Internal build system error. BuildProgram exited with code 134.
Unhandled exception. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.” can be seen
Reproducible with: 2022.3.9f1, 2023.1.12f1, 2023.2.0b9, 2023.3.0a5
Couldn't test with: 2021.3.30f1 (Different console error “The type or namespace name 'MonoBehaviour' could not be found (are you missing a using directive or an assembly reference?“))
Reproducible on: macOS 13.4.1 (M1 Max)
Not reproducible on: No other environment tested
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
This is more a feature request than a bug, as this is not supported workflow.
I do see a lot of value in it, and it is something we have planned of supporting