Search Issue Tracker
Fixed
Fixed in 1.4.5
Votes
1
Found in [Package]
1.4.2
Issue ID
DSTR-1007
Regression
No
UnitySetUp does not fail when nested coroutines throw an exception
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the Test Runner window (Window > General > Test Runner)
3. Select the “PlayMode” tab and run all tests by clicking the “Run All” button
4. Observe the Console
Expected result: Exception is thrown in the Console but the test doesn't fail and the Editor hangs
Actual result: Exception thrown in the Console fails the test and the Editor returns to its normal state
Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0a19
Reproducible on: M1 MacOS 14.2
Not reproducible on: No other environment tested
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
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
- [macOS] Rendering Debugger Volume's "Component" dropdown is opened with a big offset when "Component" field is set to any "Sample Scene"
Resolution Note (fix version 1.4.5):
Fixed an issue where UnitySetUp or UnityTearDown does not fail when nested coroutines throw an exception.