I have a similar request. Given the large impact of this change, I would have expected this to be opt-in for a while before this is enforced to give us time to adapt. As of right now, I have multiple apps that are unable to be built for testing iOS 17 due to this. The reference page "Verifying the origin of your XCFrameworks" only seems to refer to XCFrameworks manually embedded in a project and does not provide guidance for SPM dependencies nor CocoaPods.

Logged the documentation gap as FB12236685

Logged as FB15055171

I went ahead and generated a new key, but I am still unable to get this to work. The original error is gone, but now I receive a 401 error from the developer portal using Xcode 16 RC (16A242): env NSUnbufferedIO=YES xcodebuild clean archive -workspace MyApp.xcworkspace -scheme MyApp -configuration Release -archivePath results/artifacts/App.xcarchive -destination generic/platform=iOS -derivedDataPath build -allowProvisioningUpdates -authenticationKeyID **** -authenticationKeyIssuerID **** -authenticationKeyPath /Users/MyUser/MyKey.p8 GatherProvisioningInputs 2024-09-12 07:40:48.226 xcodebuild[41720:6825977] DVTServices: Received response for 0119471B-B1ED-435F-B036-97D661247558 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2024-09-12 07:40:48.393 xcodebuild[41720:6825977] DVTServices: Received response for 7A81B4FA-E41E-47BB-9C7A-D641D09BB9C2 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA}

This is quite unfortunate. Today, we pass in the allowProvisioningUpdates flag on test, archive, and exportArchive to ensure that 1) the development profile is up to date and 2) the distribution profile is up to date. This does not error when using an account signed into Xcode. The reason we are attempting to use the API is that this is the suggested workaround from FB14060904. What I’m gathering is that the API is not 1:1 with the operations Xcode can do when an account is signed in. If that is the case, I would expect some more descriptive error messages and clarifications in the man page.