Search Issue Tracker
Active
Votes
0
Found in
6000.0.26f1
6000.1.0a3
Issue ID
UUM-86897
Regression
No
Awaitable.NextFrameAsync() fails to resume when invoked multiple times from the playModeStateChanged event
Reproduction steps:
1. Open the attached “IN-88257” project
2. Open the “SampleScene”
3. Enter Play mode
4. Exit Play mode
5. Observe the Console window
Expected result: Both "Start waiting" and "Finish waiting" logs are printed
Actual result: The "Start waiting" log is printed but the "Finish waiting" log is not
Reproducible with: 6000.0.26f1, 6000.1.0a4
Couldn’t test with: 2021.3.46f1, 2022.3.52f1 (The Awaitable type doesn’t exist)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Awaitables.WaitForSecondsAsync() does not have this issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Awaitable.NextFrameAsync() fails to resume when invoked multiple times from the playModeStateChanged event
- Text input duplicates in the TextField when textField.isDelayed is set to true and typing with a Japanese keyboard layout
- “AssetDatabase.GetMainAssetTypeAtPath" returns the incorrect type when using a global namespace class with the same name as a Unity type
- Editor silently crashes when switching platforms when Meta XR Core SDK is imported
- Crash on Object::SetCachedScriptingObject when entering the Play Mode immediately after stopping asynchronous operations in the previous Play Mode session
Add comment