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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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