Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0a4
2018.3.1f1
2019.1.0a1
Issue ID
1116475
Regression
Yes
"Unloading broken assembly AML.Engine.dll, this assembly can cause crashes in the runtime"
Reproduction steps:
1. Open "AMLTestProject.zip" project
2. Reimport "AML.Engine"
3. Notice an error in the Console window ("Unloading broken assembly Assets/AML.Engine.dll, this assembly can cause crashes in the runtime")
Expected Result: Assembly works without errors
Actual Result: Assembly has errors
Fix in: 2019.2.0a7, 2019.1.0b5, 2018.3.7f1
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2018.3.0b1, 2018.3.0a5
Did not reproduce on: 2018.3.0a3, 2018.3.0a1, 2018.2.20f1, 2018.1.9f2, 2018.1.0f1, 2018.1.0a7, 2017.4.18f1, 2017.3.0a1
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
Add comment