Post not yet marked as solved
I have reported FB9647954
Post not yet marked as solved
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.
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
I can confirm when built with Xcode 10.2 removing the key, forces light mode. However, building with Xcode 11 automatically enrolls you in dark mode. My build server is using Xcode 10.2 and removing the key allows it to be published and forces light mode. "For now"
Post not yet marked as solved
It looks a though removing the key also allows for forcing light mode. I imagine it's a bug Apple has introduced as it's still listing "Light" as a valid value in the docs. Luckily it seems to remove the key altogether it achieves the same result.https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW44
