Did you ever found a solution for this ? I'm running into the main problem and the Xcode (v16.10) doesn't even see the test target of the local package in the test plan.

For clarity, I fixed the problem, with the following command : defaults write com.apple.dt.Xcode DVTDeveloperAccountManagerAppleIDLists -dict 'IDE.Identifiers.Prod' '({ "identifier" = "DEADBEEF-8599-416C-8362-E12AE4D7424F"; } )' "IDE.Prod" '({ "username" = "<apple_id>"; } )' instead of deleting the whole DVTDeveloperAccountManagerAppleIDLists. We have just updated to Xcode 16.1 so I don't know yet if it fixes the issue.

Add: I've cleared all the empty accounts, it doesn't fix the issue.

To get back on this, adding the keyID/issuerID/keyFilePath triplet to our xcodebuild commands helps, however the problem remains that even with -allowProvisioningUpdates added to all commands, exporting a built archive fails with a "no profile found for bundle xxxx" error. The only way I've found to fix this to manually open the project in Xcode on the CI machine, go to the "Signing and capabilities" tab, let the spinner run until Xcode shows it has managed things, and only then the CI pipeline will work. It seems to me this is what the -allowProvisioningUpdates is for, but it doesn't seem to work.

I'm seeing this as well on a project using multiple home-built dynamically linked xcframeworks, but they are packaged as a zip file in a single cocoapod. I think cocoapod is the culprit here.

I'm having a similar issue, with internal xcframeworks packaged in Cocoapods : Failed to build module 'Common'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)', while this compiler is 'Apple Swift version 6.0 effective-5.10 (swiftlang-6.0.0.9.10 clang-1600.0.26.2)'). Please select a toolchain which matches the SDK. The problem, is that the xcframeworks were built using Xcode 16.0, with BUILD_LIBRARY_FOR_DISTRIBUTION set to YES, but and I'm getting this error on Xcode 16.0 in an app that I'm trying to build using those xcframeworks. Update : I don't reproduce the problem when using the xcframeworks directly instead of through cocoapods, so I guess that's where the problem lies.

Same here, with Xcode 15, and about 80GB free. This is rather annoying.

I had the same issue with Xcode 14, and a device running iOS 15.7. Two different macs (running the same config), tried rebooting both and the device, nothing worked. What fixed the issue was installing Xcode 13.4.1 and preparing the device with it.

I have the same issue - my app was building properly with Xcode12 beta2, the error appeared with beta4 I believe.

This is now possible in iOS 14 : https://developer.apple.com/documentation/oslog/oslogstore