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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
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.