Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.2p3
Issue ID
942001
Regression
Yes
A particular script is not recognized as a MonoBehaviour
The script seems to be not recognized as MonoBehaviour if it is in a custom namespace AND there is a preprocessor directive:
#if UNITY_EDITOR
#else
#endif
If the empty line between #else and #endif is removed OR class is moved out of the custom namespace, everything works fine again.
To reproduce:
1. Open the project, attached by the tester (unrecognizedClass.zip)
2. Add test.cs script to any game object in the scene
Expected: a script is recognized as a MonoBehaviour regardless of whether it is in a custom namespace and there is a particular preprocessor directive
Actual: a script cannot be added to the game object, even though it is a MonoBehaviour and class name is the same as the script's name, due to the preprocessor directives and custom namespace
Reproduced in 5.5.0b5, 5.5.4p2, 5.6.2p3, 2017.1.0p4, 2017.2.0b8, 2017.3.0a4
Did not reproduce 5.4.5p4, 5.5.0b4
Regression introduced in 5.5.0b5
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
- ”Last item reached” warning is thrown when no search results are found in UI Toolkit Layout Debugger
- UI Elements overlap in the Shortcuts window when docked and resized to a smaller window size
- UIBuilder DataSourcePath dropdown fails to show properties when binding to abstract classes
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
This is a duplicate of issue #927189