Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2019.4.14f1
2020.1
2020.2
2021.1
Issue ID
1292289
Regression
No
"Cant resolve internal call" error occurs in Editor.log when running an async unit test via Test Runner
Reproduction steps:
1. Download and open the attached project: "UnityAsyncException_backup_2018_4.zip"
2. Go to Window > General > Test Runner
3. Select PlayMode and press Run All
4. Locate and open the Editor.log file
5. Press CTRL+F and search for "cant resolve internal call"
Expected result: Nothing is found
Actual result: The error occurs
Reproducible with: 2019.4.16f1, 2020.1.17f1, 2020.2.0b14, 2021.1.0a9 (Test-Framework 1.1.20)
Couldn't test with: 2018.4.30f1 (due to errors in the Console)
Note:
- Reproducible on Linux (tested on Ubuntu 18.04) and macOS, not reproducible on Windows
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
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Resolution Note (fix version 2021.2):
Fixed with the newest version of Mono in 2021.2 and 2022.1