Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
7
Found in
2018.3.0a7
2018.3.5f1
2019.1.0a1
2019.2.0a1
Issue ID
1126737
Regression
Yes
Editor throws assembly reference error when custom external assembly is used
How to reproduce:
1. Open Project UnityDllTestProject2
2. Enter the Play Mode
3. Check the console for load errors
Expected result: Project loads without errors
Actual result: Project loads with reference errors
Reproducible with: 2018.3.0a7, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Not reproducible with: 2017.4.20f2, 2018.3.0a6
Fixed in: 2018.3.10f1, 2019.1.0b7, 2019.2.0a8
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
- Wrong documentation page is displayed for the "Scene Template Pipeline" help icon
- Missing Device Simulator API
- Shadow gets cut off when in Play Mode and using shader "Shader Graph/Rotation Shader" for material
- Unable to get textureOverrideSettings from BuildPipeline.GetBuildTargetName when trying to pass in the platform string
- Getting the current process name returns Null when building with IL2CPP
PrateekP
Feb 14, 2019 05:01
This is a big set back for those who are dependent external lib and it's not working in the latest release unity version. Please consider this issue on priority.