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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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