Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a10
2019.1.4f1
2019.2.0a1
2019.3.0a1
Issue ID
1159277
Regression
No
"No MonoBehaviour in the file" when using the Assembly Definition "Version Defines" and namespace
How to reproduce:
1. Open the user's project
2. Press Play
3. Select "Main Camera" in the Hierarchy
4. Inspect the Inspector, it shows "No Behaviour In File (Script)"
The console also prints "Attached!", which comes from that script.
Expected result: MonoBehaviour in the file, the file can be attached to the GO
Actual result: No MonoBehaviour in the file
Reproducible with - 2019.3.0a7, 2019.2.0b6, 2019.1.8f1
Could not test with - 2019.1.0a9 and earlier (Version Defines was not present)
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
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a11