This seems to be fixed in iOS 14.5. I've tested on a few devices now without any problems. I don't have a solution for 14.4.2 and below however

I am seeing the same behaviour. Strangley UITest run fine with a couple of minor differences from XCode 12. But Unit tests compile and just block the simulator and won't run eventually timing out. XCode 13 RC, on Big Sur 11.6

No luck so far, I get a spindump which is a bit tricky to read after it fails. Not sure if Eskimo is about to help answer this? When I run against a iOS 14 simulator or less it works fine

I think it's a bit tricker than that unforunately. I can get you a spindump file of our project deadlocking during testing if that will help. I think it's also happening during normal function of the app too, users are reporting being stuck on a screen before the splash and the UIApplicationDelegate callbacks didFinishLaunchingWithOptions are never called. Looks like a UIKit bug causing a deadlock. I'm using Texture as a pod and I believe the deadlock is happening during some initialisation code where UIKit is called to create a layer. Looks like the deadlock is happening inside UIKit https://github.com/TextureGroup/Texture/issues/2029

I have a spindump of the running simulator after the tests timeout if it'll help Eskimo Without a good understanding on how to analyse spin dumps. I see this at the bottom of the main apps running. It looks like two threads are waiting on each other and causing the deadlock (blocked by turnstile waiting for AppName [66373] [unique pid 463253] thread 0x8ffc2e) 1-204 drive.google.com/file/d/1KhdlKf5v77cVuiOQ-T1ZUGSKrVLobCzs/view?usp=sharing

Many thanks Eskimo I will have a dig into this further. This is part of a popular UI library called Texture so I don't imagine I'm the only one facing issues with the framework initialiser and the workaround resides in a third party library.

I have reported FB9647954

I’m seeing the same behaviour and it’s causing my test repetition mode to not fire and thus it doesn’t re-run tests

So after some investigation. I found having the async setup() function caused this behaviour to prevent retries. When moving to the synchronous setup function I no longer get issue. The problem being I need to do async code in my setup... If I move my code to the following, test repetitions now work and I see no such errors override func setUp() { super.setUp() continueAfterFailure = false // setup async seems to prevent test repetitions from working let exp = expectation(description: "setup") Task { try await setupWebApp(router: router) exp.fulfill() } wait(for: [exp], timeout: 10) }