Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.0
Issue ID
DSTR-1025
Regression
Yes
Editor gets stuck in the temporary playmode tests Scene when playmode tests are ran
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Open the Test Runner Window (Window > General > Test Runner)
4. Run the PlayMode Tests (“Run All” button from the PlayMode tab in the Test Runner Window)
5. Observe the Game View
Expected result: The Editor returns to the previous Scene with a Cube GameObject in the middle
Actual result: “All tests succeeded“ is seen in the Game View without the ability to return to the original Scene
Reproducible with: 2023.3.0a16, 2023.3.0b6
Not reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0a15
Reproducible on: M1 MacOS 14.2, Windows 11 (User’s platform)
Not reproducible on: No other environment tested
Comments (2)
-
Aldeminor
Sep 13, 2024 07:59
Nevermind, I managed to update the package manually by name (its strange that the Package Manager does not allow automatic update although 1.4.4 seems compatible with 2022.3.32)
-
Aldeminor
Sep 13, 2024 07:55
Will there be a fix for 2022 LTS? The latest Test Framework package available is 1.4.3 where the error is still occurs.
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
- Unity Version Control window during "Create workspace" updates only when the mouse is moved
- Crash on AudioMixer::GetFloat when entering Play Mode in a specific project
- Test assembly files are not generated when using a local package included in a subdirectory
- URP Terrain Shaders are always included when building on any target platform
- Multiple errors thrown and Scene/Game view is not rendered when Lighting Override Mask is set to the same layer as the Volume
Resolution Note (fix version 1.4.4):
The playmode contoller is now set and cleaned up correctly, ensuring that the scene is displayed correctly after a test run.