Thanks for your answer @eskimo, but I was looking forward to find a fix for the warning, which I haven't found it exists at the moment. So far, my understanding is that Runloop methods have been declared not async safe (which is understandable), but without adding an async alternative so far. So, at the moment, there are no fixes to this warnings, and instead it would be needed to avoid using Runloops in async contexts.

Thanks for the links and sorry to haven't followed up quicker. I think I've not been able to explain what I expect to achieve (or even if it ever will be possible), I hope this time I will. I understand that swift concurrency actors/Tasks are not in the same conceptual world than Runloops/Threads. What I would expect to be able to do is to replace the Runloop code with something equivalent to RunLoop.current.run(until: Date()) but in Tasks/Actors world. await MainActor.run(forInterval: 0.1) Or even better, what I would really like to achieve is to replace that piece of code (that Runloop snippet that I've copycat from some people unit tests code) that tries to force UI events processing.

I needed to rollback to Xcode 15.0.1 to avoid the horrible popup party.

Did anyone find any solution?

Using Xcode 15.2 and I've found in Console log app some more log info about the crashes: "ManagedAppDistributionDaemon/Main.swift:38: Fatal error: Unable to obtain device information" Also there are LOTS of crashes logged.