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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a11