Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2019.2.X, 2019.3.X

Votes

3

Found in

2019.2

2019.2.0b5

2019.3

Issue ID

1160664

Regression

Yes

Custom built DLL's scripts which have classes derived from UIBehaviour cannot be added as a component anymore

Scripting

-

How to reproduce:
1. Download and extract the attached 'DLLScripts.zip' archive somewhere on your computer (there are two scripts, NewBehaviourScript.cs and NewBehaviourScript2.cs)
2. Download and extract the attached '1160664repro.zip' project
3. Navigate to the Editor directory
4. Run this command from the Windows PowerShell:
"./Unity.exe -batchmode -nographics -projectPath "path_to_the_project_directory" -executeMethod "MLPluginBuilder.BuildSelected" -assemblyName "Assets\Custom.dll" -scripts "path_to_the_DLLScripts_directory" -allowUnsafeCode "true" -quit -logfile"
5. Once the DLL is built in the Assets folder, open the project
6. Try to add both scripts as a component to any GameObject

Expected results: Both scripts are eligible to add as a component
Actual results: NewBehaviourScript cannot be added since it derives from BaseInputModule while NewBehaviourScript2 can be added since it derives directly from MonoBehaviour

Reproducible with: 2019.2.0f1, 2019.3.0a11
Not reproducible with: 2019.1.13f1 and below

Notes:
- This is happening because UGUI broke out as a separate package
- Happens with any class that derives from UIBehaviour

Add comment

Log in to post comment