Search Issue Tracker
Fixed
Fixed in 2022.2.9f1, 2023.1.0b5, 2023.2.0a3
Votes
1
Found in
2022.2.4f1
2023.1.0b1
2023.2.0a1
Issue ID
UUM-25109
Regression
Yes
“MonoBehaviour” is not recognized in Script files when “additionalfile” parameter is used in “csc.rsp” file
Reproduction steps:
1. Open the attached project “NoMonoRepro”
2. In the Project window select “Assets/Test” script file
3. Look at the Inspector window
Expected result: Inspector window shows the “Test” script contents
Actual results: Inspector shows “No MonoBehaviour scripts in the file, or their names do not match the file name”
Reproducible with: 2022.2.0a3, 2022.2.4f1, 2023.1.0b1
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.0a2
Reproducible on: macOS 13.1 (Intel)
Note: There is no repro if line 3 is commented or deleted in “Assets/csc.rsp” file
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Add comment