Search Issue Tracker
Fixed
Fixed in 2021.3.33f1, 2023.1.17f1
Votes
0
Found in
2021.3.28f1
2022.2.5f1
2023.1.4f1
Issue ID
UUM-45273
Regression
No
[General] AsyncOperation returned by Screen.MoveMainWindowTo never triggers a completed event when the Player is moved
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Build And Run
4. In Player press the button with the text “Go To Next Monitor“
5. Open the Player.log file
6. Observe it
Expected result: “Async operation completed” is seen
Actual result: “Async operation completed” is not presented
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a1
Fixed in: 2023.2.0a2
Reproduces on: Windows 10 Enterprise 21H2
Notes:
- Fails to move to the left monitor if the Player is opened on the right monitor
- The "completed" event is fired successfully in the editor (where the function doesn't actually do anything, as expected)
- The fact that the "completed" event is not fired causes awaiting the async operation to never end in UniTask since its awaiter is listening for the "completed" event
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
Add comment