Search Issue Tracker
Won't Fix
Votes
2
Found in
5.6.0f3
Issue ID
929696
Regression
No
"No MonoBehaviour scripts in the file" error if classes of the script are inside the namespace
"No MonoBehaviour scripts in the file" error if classes of the script are inside the namespace and the one which derives from MonoBehaviour is not the first one declared.
Reproduction steps:
1. Open the attached project
2. Select "NameSpaceBugExample" script in the Project window
Expected: no error
Actual: "No MonoBehaviour scripts in the file <...>" error
Reproducible on: 5.4.5p2, 5.5.0p4, 5.6.0f3, 2017.1.0f2, 2017.2.0b2
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.