The way I went around this in Bitrise is that I manually uploaded a development certificate to Bitrise. Bitrise then uses this uploaded certificate to code sign the archive instead of fetching the certificate from Apple. The other code signing files are then fetched properly and it works as expected. I believe this is a workaround though and the command should fetch an already existing development certificate fine without attempting to create a new one.

I am getting exactly the same behavior using the Bitrise CI. Success on the first try and this same error on the subsequent. Multiple development certificates are really created on the Apple Developer portal. When revoked, this works again. xcodebuild "-project" "/Demo.xcodeproj" "-scheme" "Bitrise Demo" "-configuration" "Release" "-xcconfig" "/temp.xcconfig" "archive" "-archivePath" "/Demo.xcarchive" "-allowProvisioningUpdates" "-authenticationKeyPath" "/AuthKey_YGHQQ95LVN_1271060667.p8" "-authenticationKeyID" "YGHQQ95LVN" "-authenticationKeyIssuerID" "e053-5b8c7c11a4d1" "-destination" "generic/platform=iOS"