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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a11