Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f1
2019.1.0a1
2019.2.0a1
Issue ID
1117125
Regression
No
MonoBehaviour Components cannot be added through Editor when they are compiled into Assembly using Unity
Reproduction steps:
1. Open the Project inside of "Unity Assembly Bug.zip"
2. Play the "SampleScene" and select any "Dynamically added component" GameObject
3. Inside the Inspector click on "Add Component" and search for "ExampleBehaviour"
Expected: "ExampleBehaviour" appears in the list
Actual: "ExampleBehaviour" does not appear in the list
Reproduced on: 2017.4.20f2, 2018.3.6f1, 2019.1.0b4, 2019.2.0a6
Note:
- In the 2017.4 stream, Editor allows the addition of MonoBehaviour script inside of the .dll module, but when selected it will still display a warning due to the script not being loaded
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
- 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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (fix version 2019.3):
The issue in this project is there is a .dll that has the same filename as a .asmdef. This will be fixed by emitting an actionable error about this.