UniTask.Delay results in "Pending" status forever
See original GitHub issueI’m trying to use “await UniTask.Delay”, but every time that line gets executed, the UniTask Tracker lists two new entries with status pending (“UniTask.DelayPromise” and “UniTask.CompletionSource”).
private void startMethod()
{
StartCoroutine(UniTask.ToCoroutine(asyncMethod));
}
private async UniTask asyncMethod()
{
//do something
await UniTask.Delay(5000);
//do something
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
c# - Synchronously waiting for an async operation, and ...
Unfortunately, code using Wait (or Result ) will block a thread in that context, so the async method cannot complete.
Read more >Async methods continue to execute when you stop the ...
Delay just does a normal Task.Delay and if we are not in play mode after that it awaits a forever-pending task
Read more >UniTask v2 — Zero Allocation async/await for Unity, with ...
As a limitation, all UniTask objects cannot await twice, as they automatically return to the pool when the await completes. This constraint is ......
Read more >COMBATING ACID VIOLENCE IN BANGLADESH, INDIA, ...
Such delays tend to hurt prosecutions' cases, as victims and witnesses lose interest and as physical evidence deteriorates or disappears.291.
Read more >Napanee Beaver June 25 2015
The predictable result will be a continuation of the horrible divide in our community and on council. We do not deserve this in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
UniTask already uses GetCurrentPlayerLoop but ECS does not(uses GetDefaultPlayerLoop). You should complain to ECS.
@neuecc I’m not using ECS in my project, but the following fixed the issue:
I checked my current 2019.2 assets/plugins vs. my new 2019.3 ones, and there’re no major differences in assets/plugins, so it somehow looks like it is a 2019.3 issue in combination with “something”.