The technique we recommend instead is to have your developer’s submit an Xcode archive (.xcarchive). Interesting. Thank you for the detailed response! Looking at the help for xcodebuild, we might get what we need with the exportArchive option an options plist with: provisioningProfiles with application-identifier(?) as keys and profile names as values signingCertificate with our certificate name installerSigningCertificate, with our cert name (might not be necessary, not sure) destination, value of upload (our developers use the App Store even for an enterprise deployment) method, value of app-store teamID, our corporate "team ID" signingStyle, value of manual uploadSymbols , value of false In any case, this will something new to try, and it could make our lives simpler if it works!

Hmm, we've been informed of some process-related snafus on the part of the submitters. Not sure what they would be yet. This post, I think, can wait for a bit.