Search Issue Tracker
Third Party Issue
Third Party Issue in 1.8.X
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
BUR-2070
Regression
Yes
"Failed to resolve assembly" error in the Console when reloading Scripts
How to reproduce:
1. Open the attached user project
2. Press “Reload Scripts“ (Tools > Reload Scripts)
Expected result: Scripts are reloaded with no errors in the Console
Actual result: Scripts are reloaded with the “Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: ‘0Harmony, Version=2.1.1.0, Culture=neutral, PublicKeyToken=null'“ error in the Console
Reproducible with: 1.8.0-pre.2 (2021.3.11f1, 2022.1.18f1, 2022.2.0b9, 2023.1.0a13)
Not reproducible with: 1.7.4, 1.8.0-pre.1 (2021.3.11f1, 2022.1.18f1, 2022.2.0b9, 2023.1.0a13)
Can’t test with: 1.7.4, 1.8.0-pre.1, 1.8.0-pre.2 (2020.3.40f1) (error CS0246: The type or namespace name 'NUnit' could not be found)
Reproduced on: macOS (12.5)
Note: Downgrading and upgrading the Burst package solves the issue, but after restarting Unity, the issue comes back
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
- "Trying to access the DPI setting of a visual element that is not on a panel." warning thrown when entering/exiting Play Mode with new Hierarchy not displayed
- Transparent geometry does not render in Built-in Renderer Deferred mode when a custom post-processing effect is enabled on Mac with Metal API
- BuildVectorImage(SceneInfo, Rect) is internal, and should be public
- SVGImporter preset added to the Preset Manager changes to a ScriptedImporter when restarting the project
- Built-in Standard shader variants remain stripped from the build when retained via Shader Variant Collection or Shader Build Settings
Resolution Note:
This error happens because the a precompiled dll in the com.needle.editorpatching package has an assembly name that doesn't match the assembly's filename.
Specifically, the filename is "EditorPatching_0Harmony.dll", while the assembly name is "0Harmony".
For reference, here's the package repo where that dll is located: https://github.com/needle-tools/editorpatching/tree/main/package/Editor/Plugins
Burst doesn't support this scenario. Burst requires that the assembly name matches the filename.
I suggest contacting the authors of the com.needle.editorpatching package to see if they can recompile the EditorPatching_0Harmony.dll, making the assembly name "EditorPatching_0Harmony".
Resolution Note (1.8.X):
This error happens because the a precompiled dll in the com.needle.editorpatching package has an assembly name that doesn't match the assembly's filename.
Specifically, the filename is "EditorPatching_0Harmony.dll", while the assembly name is "0Harmony".
For reference, here's the package repo where that dll is located: https://github.com/needle-tools/editorpatching/tree/main/package/Editor/Plugins
Burst doesn't support this scenario. Burst requires that the assembly name matches the filename.
I suggest contacting the authors of the com.needle.editorpatching package to see if they can recompile the EditorPatching_0Harmony.dll, making the assembly name "EditorPatching_0Harmony".