Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.2.X
Fixed in 2023.1.0b9, 2023.2.0a9
Votes
0
Found in
2021.3.7f1
2021.3.8f1
2022.1.11f1
2022.2.0b3
2023.1.0a14
2023.2.0a1
Issue ID
UUM-14481
Regression
Yes
Linker Error: I18N assembly cannot be resolved
Reproduction steps:
1. Open the user’s attached project
2. Build the “SampleScene” scene with the IL2CPP backend
Expected result: Project builds with no errors
Actual result: Build fails with “Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'I18N, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null” error
Reproducible with: 1.7.2 (2021.3.7f1), 1.7.3 (2022.1.11f1), 1.8.0-pre.1 (2022.2.0b3, 2023.1.0a4)
Not reproducible with: 1.7.1 (2020.3.37f1)
Notes:
- Does not reproduce with Mono backend, but sometimes causes a crash
- Does not reproduce when the Burst package is removed
- Similar issue: [https://issuetracker.unity3d.com/issues/build-fails-with-error-mono-dot-cecil-dot-assemblyresolutionexception-failed-to-resolve-assembly-when-unity-iap-is-in-the-project]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Vertex data is displaced when building with Addressables with Optimize Mesh Data enabled
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
Add comment