Search Issue Tracker

Fixed in 2018.3.X

Votes

11

Found in

2018.1.0b5

Issue ID

996976

Regression

No

"Unloading broken assembly" error message provides insufficient information

Scripting

-

Steps to reproduce:
1. Open attached project "UnloadingBrokenAssemblyError.zip"
2. Upon launch you will see the "Unloading broken assembly Assets/Microsoft.ProjectOxford.Face.dll, this assembly can cause crashes in the runtime" error
3. The .dll is just missing dependencies which you can import from attached "MissingDependencies.zip"

Expected: The manifest of the DLL has information about dependencies, which could be exposed and shown in the error message for clarity
Actual: Error message says dll is broken which could mean a multitude of things

Reproduced on 2018.1.0b7, 2018.1.0b1

Compilation errors on anything earlier than 2018.1

Comments (18)

  1. ItsBaptiste

    Jun 19, 2021 08:45

    Reproduced on Unity 2019.4.12f1 Windows10 64bit

  2. siqing_0423

    Apr 25, 2019 03:21

    Reproduced on Unity 2018.3.13f1 Windows 10 64bit

  3. gssarvba

    Feb 21, 2019 03:15

    Reproduced in 2018.3.0f2 windows 10

    Unloading broken assembly Library/ScriptAssemblies/Assembly-CSharp-Editor.dll, this assembly can cause crashes in the runtime

  4. Buswolley

    Feb 11, 2019 22:15

    Encountered on 2018.3.5f1, OSX

  5. softone

    Feb 09, 2019 11:44

    Reproduced on Unity 2018.3.4f1 on Windows 10

  6. m0guz

    Nov 01, 2018 20:45

    Reproduced on Unity 2018.3.0b8, only happens when Scripting Runtime set to .NET 4.x . Error disappears when I set .NET 3.5.

    The thing I noticed is error happens when loading DLL built with .NET 3.5

  7. Nanorock

    Oct 16, 2018 11:37

    Reproduced on Unity 2018.3.0b5 Windows10 64bit. Still not fixed

  8. snarlynarwhal

    Oct 05, 2018 20:07

    Reproduced on Unity 2018.3.0b4 Windows10 64bit. Error message still has no useful information.

  9. JuozasK

    Oct 01, 2018 08:28

    This bug has been fixed in Unity 2018.3

    Currently, there is no plan to backport it to older versions.
    Use the newer Unity version to avoid encountering this bug :)

  10. horeaper

    Sep 30, 2018 04:17

    Reproduced on Unity 2018.2.1f1 Windows 10 64bit

Add comment

Log in to post comment