Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.2.0a1
2018.3.0f2
Issue ID
1111243
Regression
Yes
Exception is not handled properly in PlayTests when a custom Enumerator is used as a Coroutine and throws an Exception
To reproduce:
1. Download attached project “PlayModeTestExceptionHandling.zip" and open in Unity
2. Open Test Runner window
3. Press the "EditMode" button
4. Press "Run All" button
Expected results: Tests almost immediately fails
Actual results: ExceptionTestWithEnumeratorPasses test never finishes running
Notes:
- This issue appears on both Windows and macOS
- The same problem happens when you Assert in a Unity Test in hasNext
Reproduced on Unity 2018.2.0a1, 2018.2.20f1, 2018.3.1f1 and 2019.1.0a13
Not reproduced on Unity 2018.1.9f2
Regression on Unity 2018.2.0a1
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