Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.2.X, 2021.1.X
Votes
3
Found in
2019.4
2020.1
2020.2
2020.2.0b9
2021.1
Issue ID
1289863
Regression
No
IL2CPP stack trace does not match MONO scripting back end when async/await is used
Reproduction steps:
1. Open the attached project ("2019Repro.zip")
2. Open the "SampleScene" scene
3. Enter Play mode and press a button in the middle
4. Open the Console window and observe the error
5. Make sure IL2CPP is set as scripting backend (Player->Other Settings->Configuration)
6. Build and Run the project as a development build
7. Press the button in the middle and observe the error in the Console
Expected result: Errors matches
Actual result: Error in the IL2CPP build is different than in the editor
Reproducible with: 2019.4.16f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0a10
Could not test with: 2018.4.30f1 (Project fails with error: Multiple precompiled assemblies with the same name nunit.framework.dll)
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
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
- Inspector window's ObjectFields are not updating correctly
- Linker error when building with the MRTK Graphics Tools package and Managed Stripping Level is set to High
Resolution Note (fix version 2021.2):
Fixed with 2021.2.0a3, backported to 2021.1.0b5, 2020.2.5f1, 2019.4.21f1