Odd bug. My unfortunate workaround is to use CIDetectorAccuracyLow, in the case that we're on an iOS simulator: #if targetEnvironment(simulator) let detectorAccuracy = CIDetectorAccuracyLow #else let detectorAccuracy = CIDetectorAccuracyHigh #endif let options = [CIDetectorAccuracy: detectorAccuracy] let faceDetector = CIDetector(ofType: CIDetectorTypeFace, context: nil, options: options) I don't love the solution, as it seems like the type of hack that will remain, forgotten, in the codebase, quietly confusing future developers, for the rest of eternity. But, low accuracy works on Simulator and I suppose it doesn't matter too much so long as production users still get the high accuracy detection.

I had the issue, but in an framework that was defined in my own codebase, rather than an external framework like UnityFramework, AVFoundation, etc. Since it was something that was in my code, I couldn't add and remove the framework as @codethislab suggests. If anyone else is in this situation, my the solution was a fresh checkout from the Git repository. It's a bit annoying, as I'm losing some stashed code, but hey, at least I can upload to AppStoreConnect now 🤷‍♂️