Search Issue Tracker
Won't Fix
Won't Fix in 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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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
Resolution Note (2023.3.X):
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