I'm having trouble generating an IPA for OTA distribution.
We made an app for another company. That other company added me on their Enterprise account so that I could distribute using their signing identity.
Creating the ipa with the command line
Using the command xcodebuild, an archive I made using xcode where I put the team as that other company's team, and a plist stating I was building for Enterprise, I get this error:
No valid iOS Distribution signing identities belonging to team [company team id of the other company] were found.
Using XCode
I tried doing it with XCode as well, unchecking the "Automatically manage signing" in Xcode and selecting the other company, and then I get these errors:
No signing certificate "iOS Distribution" found.
No "iOS Distribution" signing certificate matching team ID [other company's team ID] with a private key was found."
Is there something I should download from the developer account? (I already downloaded all the certificates... I think) I can't revoke the distribution certificate they have, as it is not my company and it might create problems for them.
Thanks.
A distribution certificate identifies your team/organization within a distribution provisioning profile and allows you to submit your app to the Apple App Store. A . p12 file contains the certificates Apple needs in order to build and publish apps.
To get a certificate, you need to generate a Certificate Signing Request with Keychain Access and send it to Apple. This will create a public/private key for you if you don't have one already. Apple will then verify the information, and create a certificate for you.
If your certificate is revoked, your passes will no longer function properly. If your Apple Developer Program membership is valid, your existing apps on the App Store won't be affected. However, you'll no longer be able to upload new apps or updates signed with the expired or revoked certificate to the App Store.
When you downloaded every certificate from the developer account, you only downloaded the public keys, what you need to do is one of two solutions that I know of:
Either ask the other company to export one of the private key from one of their machine, and you can import it into your keychain, only then when you'll try to sign your app, it will look for private half of the certificate in the keychain and it will find it (hence the error you're getting, no certificate with PRIVATE KEY was found).
Or, you'll have to create a new production Certificate using a certificate generated from your own keychain (and a provisioning that goes with it...).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With