Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
2020.1.0a11
Issue ID
1199558
Regression
No
[TestRunner] Calling a Coroutine which waits for a few frames in Edit Mode Tests will freeze the test runner
Reproduction steps:
1. Open "coroutine_delay.zip" project
2. Open the Test Runner
3. "Run All" Edit Mode Tests
Expected Result: All tests finish running
Actual Result: Process freezes on Test 4 which waits for a few frames
Error:
"EditMode test can only yield null"
Reproduced with: 2020.1.0a14, 2019.3.0b12, 2019.2.13f1, 2018.4.13f1, 2017.4.35f1
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Coroutines only work in play mode and cannot be used during an EditMode test or in the editor.