Search Issue Tracker

Fixed in 2022.2.X

Votes

0

Found in

2019.3.0b5

2019.3.1f1

2020.1.0a6

2020.2

Issue ID

1223295

Regression

Yes

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

Scripting

-

How to reproduce:
1. Open user-submitted project (testB.zip)
2. See that Assets/Plugins/testUIDLL contains Class1
3. Close the project
4. Delete the Library folder
5. Open the project again
6. See testUIDLL again

Expected result: testUIDLL contains Class1
Actual result: testUIDLL does not display Class1 until it is renamed/reimported

Reproducible with: 2019.3.0b5, 2019.3.4f1, 2020.1.0a6, 2020.1.0a25, 2020.2.0a1
Not reproducible with: 2017.4.37f1, 2019.3.0a2
Could not test with: 2019.3.0a3, 2019.3.0b4, 2020.1.0a1, 2020.1.0a5(UnityEngine.UI assembly errors or .dll does not display classes even when reimported)

  1. lukaszunity

    May 05, 2020

    The problem is that the Custom.dll is referencing an assembly that Unity compiles, when Unity imports, we import DLL's before Script Assemblies.
    As a temporary fix you can add this Editor Script
    This will reimport the dll after the first domain reload.
    https://gist.github.com/hknielsen/1b2712f2fc38c768bd6938e2375eb563

  1. Resolution Note (fix version 2022.2):

    Fixed in: 2022.2.0a3

Log in to vote on this issue

Comments (2)

  1. JiawenYu

    Dec 03, 2020 06:50

    Is there any progress?

  2. unity_nDI54UEnEZerWg

    Aug 09, 2020 02:56

    Is there any progress?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues