Search Issue Tracker
By Design
Votes
0
Found in
2018.2.0a1
2018.2.0b4
Issue ID
1040539
Regression
Yes
[UTR] EditorApplication.isPlaying = false doesn't stop playmode after test completion
Steps to reproduce:
1) Open the attached project.
2) Open Test Runner.
3) Run EditMode tests.
The tests pass, but the editor remains in playmode, even though EditorApplication.isPlaying = false; is set.
Expected: playmode stops after test completion.
Actual: playmode remains active after test completion.
Reproduced on:
2018.3.0a1, 2018.2.0a1
Did not reproduce:
2018.1.0b1
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
- 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
Resolution Note:
EditorApplication.isPlaying can not be used to enter/exit playmode. yield return new EnterPlayMode(); and yield return new ExitPlayMode(); should be used instead.
https://docs.unity3d.com/2018.3/Documentation/ScriptReference/TestTools.EnterPlayMode.html