Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.43f1
Issue ID
UUM-78489
Regression
No
"Fatal error in Unity CIL Linker Mono.Linker.LinkerFatalErrorException: ILLink: error IL1013" is thrown when building for UWP
How to reproduce:
1. Open the attached project "VR.zip"
2. Buid the project for UWP
Expected results: Build is successful
Actual results: Build fails with error "Fatal error in Unity CIL Linker Mono.Linker.LinkerFatalErrorException: ILLink: error IL1013"
Reproducible with: 2022.3.43f1
Not reproducible with: 2021.3.43f1, 6000.0.16f1
Reproducible on: Windows 10 22H2
Not reproducible on: Windows Standalone
Notes:
Only reproducible with UWP
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. Given this bug only happens in 2022.3, which is in Extended LTS now, and newer versions of Unity do not reproduce it, the decision was made to not fix it and close it for now.
Let us know if there is anything else that changes the impact or severity of this issue, in which case we can re-open it.
Thank you again for taking the time to report this issue
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. Given this bug only happens in 2022.3, which is in Extended LTS now, and newer versions of Unity do not reproduce it, the decision was made to not fix it and close it for now.
Let us know if there is anything else that changes the impact or severity of this issue, in which case we can re-open it.
Thank you again for taking the time to report this issue