Search Issue Tracker
By Design
By Design in 2022.2.X
Votes
1
Found in
2022.2.0a13
Issue ID
UUM-610
Regression
No
[IL2CPP] Fatal error in Unity CIL Linker error is thrown when .dll filename does not match assembly name
Reproduction steps:
1. Open the attached user's Unity project "ErrorReport.zip"
2. Go to File > Build Settings and switch to Android Platform
3. Go to Player Settings and make sure that IL2CPP Scripting Backend is selected
4. Go back to Build Settings and Build the project
5. Observe errors appear in the Console window
Expected result: The build is successful
Actual result: The build fails, errors are thrown in the console window: "Fatal error in Unity CIL Linker
System.InvalidOperationException: No action for the assembly ICSharpCode.SharpZipLib"
Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.17f1, 2022.1.0b13, 2022.2.0a9
Notes:
- The issue is reproducible when building for iOS
- The issue is not reproducible with Mono Scripting Backend selected
- The issue is not reproducible when building for Standalone
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We don't support file names that differ from the assembly name.
Resolution Note (2022.2.X):
We don't support file names that differ from the assembly name.