Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.1.0a5
2019.3.0b9
Issue ID
1196416
Regression
Yes
"Could not load file or assembly" error when assembly dependency is in another folder
How to reproduce:
1. Open the attached project
2. Reimport the System.IO.Pipelines.dll file.
Actual result: Errors are thrown.
Expected result: No errors are thrown.
Reproducible with: 2020.1.0a13, 2019.3.0b11, 2019.2.13f1, 2018.4.13f1, 2018.2.21f1, 2018.1.9f1, 2018.1.0a5.
Regression introduced in: 2018.1.0a5.
Not reproducible with: 2017.4.34f1, 2018.1.0a1, 2018.1.0a4.
Notes:
- The errors are caused because System.IO.Pipelines has references to Libs/System.Buffers and they are in a separate folders.
- The errors:
Error: Could not load signature of System.IO.Pipelines.PipeCompletionCallbacks:.ctor due to: Could not load file or assembly 'System.Buffers,
Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. assembly:System.Buffers, Version=4.0.2.0,
Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 type:<unknown type> member:(null) signature:<none>
Unloading broken assembly Assets/System.IO.Pipelines.dll, this assembly can cause crashes in the runtime
Comments (4)
-
ScottAdams
Nov 04, 2020 16:35
There seem to be working on this according to this thread (See Harold Nielsen comment 9/4/20)
-
maxiboch
Oct 07, 2020 21:17
Still seems to be an issue, a fix for this would be huge for our team.
-
bfoddy
Oct 07, 2020 21:06
This is not fixed in 2020.1.8f1
-
Bortos
Feb 21, 2020 06:45
Any new information? The issue is marked as fixed in 2020.1. I have tested on 2020.1.0a23 and this still seems to be an issue.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2020.1):
The issue is the references to System.Buffers.dll
References in a DLL that is strong named needs to exact match. In this case System.IO.Pipelines.dll references System.Buffers.dll(Version 4.0.2.0), where the System.Buffers.dll version in the project is 4.0.3.0.
That it works when in the same folder seem like a bug in Mono that we will investigate.
We will add better information about this so its clear what version we expect