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
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)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
max_payne
Jul 17, 2018 14:35
Reproduced on Unity 2018.1.1f1 Windows10 64bit
AdrianGarciaM
Jun 08, 2018 19:58
Reproduced on Unity 2018.1.1f1 Windows 10 64 bit
Wurstbeschleuniger
Jun 08, 2018 00:26
Reproduced on Unity 2018.1.0f2 Windows 10 64bit
Basic50
May 30, 2018 14:56
Reproduced on Unity 2018.1.2f1 Mac OS High Sierra V 10.13.4
NanoMath
May 18, 2018 10:28
Reproduced on Unity 2018.2.0b4 Windows10 64bit