xcodebuild should use App Store Connect API Key for uploading to App Store with -exportOptionsPlist destination as upload

Number:rdar://FB9145847 Date Originated:Jun 9, 2021 at 8:38 AM
Status:Open Resolved:
Product:Xcode Product Version:Xcode 13.0 - Beta 1 - 13A5154h
Classification: Reproducible:
I'm trying to use the `xcodebuild` CLI tool to upload to the App Store with the "upload" value for "destination" in the "-exportOptionsPlist". Historically the only authentication method has been Apple ID. 

Xcode 15 adds support for the App Store Connect API Key. This API Key is used for `-allowProvisioningUpdates` but it isn't working for the "upload" destination.

The reason I am trying and hoping to use upload to the App Store with `xcodebuild` is because I want to make use of the new ability to manage version number and build numbers. This is done by adding the “manageAppVersionAndBuildNumber” in the “-exportOptionsPlist”. 

This does work, however, the “manageAppVersionAndBuildNumber” and “upload” only work with the Apple ID that is signed into Xcode through the preferences. Getting and updating the app version and build number and uploading the binary are all possible to do with the App Store Connect API Key in other tools.

FEATURE SUGGESTION: Allow “manageAppVersionAndBuildNumber” and “upload” in "-exportOptionsPlist" to use the App Store Connect API Key information passed in through “-authenticationKeyPath”, “-authenticationKeyID”, and “-authenticationIssuerID” so having a logged in Apple ID through Xcode is not required


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!