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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment