I've been going through this, trying to move an app from a corporate account to a personal account. Could not transfer because it used CloudKit. First try was to just build the app on the new account - Apple rejected it as spam, probably because they figured out it was similar to the app on the corp account. DTS said basically to delete the old app, then quickly grab the name for the new one. For now, I've built a "premium" version of the app without CloudKit on the corp account, will try to migrate users there, then transfer that new app. I'll be back to let you know how it goes.

I had all the settings correct. Ultimately fixed the issue by creating a new project and moving all the existing code over there. It's possible that it was caused by having one target for iOS, and a second for Mac, and trying to share the same umbrella header file between the two. But it's fixed now, so I'm not going to bother with verifying the problem ;-)

I experienced this issue a couple of days ago. The message about "CoreAudioTypes" is completely misleading. In my case, the cause was that while removing some old code I had accidentally deleted a class that was still required. However, the only message that popped up when building was about "CoreAudioTypes" - when I restored the missing class, the message went away and the app built successfully. You can try hunting around in the build logs for more detail when you see this. Bottom line: When you see "CoreAudioTypes" it's almost certainly a red herring - you've messed up something else.

Same problem for me. I could not figure out how to find an older version of Xcode, so created class files and changed them by hand.

Never mind. My mistake. I left some old testing schemes around (11 months ago), and didnt' quite remember the correct way to run these tests. All is good.

Never mind. Turns out you can't actually do this directly with SecKeyCreateWithData, you have to switch to Swift CryptoKit. See: https://developer.apple.com/forums/thread/680572 func createSecKeyWithPEMSecp256r1Private(_ pem: String) throws -> SecKey { let privateKeyCK = try P256.Signing.PrivateKey(pemRepresentation: pem) let x963Data = privateKeyCK.x963Representation var errorQ: Unmanaged<CFError>? = nil guard let privateKeySF = SecKeyCreateWithData(x963Data as NSData, [ kSecAttrKeyType: kSecAttrKeyTypeECSECPrimeRandom, kSecAttrKeyClass: kSecAttrKeyClassPrivate, ] as NSDictionary, &errorQ) else { throw errorQ!.takeRetainedValue() } return privateKeySF }

I'm still seeing this warning today, March 6, 2026. It's completely unreasonable for Apple to leave this unfixed for 4+ months!