Not to say you should always use Async-Await instead of Coroutine, just an alternative for whoever may be reading this, as Async has return values, threading, not tied to monobehaviour, overall better suited for User Input ( on click in this case ) and device or network IO.

That talk from Unite Copenhagen 2019 I linked in my last comment goes over some best practices for both Coroutine and Async, and rules of thumb on which you should use depending on what you need.

While Coroutines haven't "officially" been replaced or deprecated, the general recommendation from Unity and other devs seems to be to use Async-Await instead of Coroutine when possible. Which provides several benefits beyond whatever was causing this particular reported issue.

More info:

Best practices: Async vs. coroutines - Unite Copenhagen 2019
https://www.youtube.com/watch?v=7eKi6NKri6I

Async-Await instead of coroutines in Unity 2017
http://www.stevevermeulen.com/index.php/2017/09/using-async-await-in-unity3d-2017/

It is actually not resolved, happens for me too which is a no-go for development. At least some fix or workaround temporarily would be good.

It is actually not resolved, happens for me too which is a no-go for development. At least some fix or workaround temporarily would be good.