Search Issue Tracker
Active
Votes
0
Found in [Package]
1.1.20
Issue ID
DSTR-69
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Add comment