Search Issue Tracker
Active
Votes
0
Found in [Package]
2017.3.0a1
2018.2.6f1
2018.3.0a1
2019.1.0a1
Issue ID
1112534
Regression
No
The `finally` block is not called in UnityTest if error message is logged
Steps to reproduce:
1. Download 1112534_repro.zip project
2. Run test in play mode
Expected results: Code in both "try" and "finally" blocks are called
Actual results: Code "finally" block isn't called
Reproduced with:2019.1.0a13, 2018.3.2f1, 2017.4.18f1
Example code:
[UnityTest]
public IEnumerator FinallyNotCalled()
{
try
{
Debug.LogError("a");
yield return null;
Debug.Log("b");
}
finally
{
Debug.Log("finally");
}
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment