Search Issue Tracker
Won't Fix
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.19f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-17066
Regression
No
IL2CPP Build fails when UniTask variable is declared in the struct
Reproduction steps:
- Open the attached project (“IL2CPPUniTaskBug.zip“)
- Select Scene Assets/Scenes/SampleScene
- Build Project File>Build And Run
Expected results: Build completes
Actual results: Build fails
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Reproduced on: Windows 11
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Resolution Note:
This is a limitation of il2cpp (.Net Framework and CoreCLR). At code generation time and at runtime il2cpp processes instance and static fields at the same time. Your case creates a circular dependency between `Result` and the inflated `UniTask<Result>`.
We do not plan to fix this in il2cpp as CoreCLR also does not handle this case and we are in the process of adding CoreCLR support to the Unity Player.
If Microsoft decides to fix this issue we will re-evaluate the bug for il2cpp.
https://github.com/dotnet/runtime/issues/5479