Upload your iOS certificates
This section is for iOS apps. If your app is an Android app, skip this section and see Invite testers to try your Android app.
Before we can invite testers to test your iOS app, buddybuild requires your Code Signing Identities and Provisioning Profiles to create signed device builds.
All apps to be installed on iOS devices must be signed with a code-signing identity. Buddybuild cannot create a code-signing identity for you, you need to do that through Xcode, or the Apple Developer Portal. For more information, see Maintaining Your Signing Identities and Certificates in Apple’s documentation.
Finding and uploading specific items from your keychain can be painful and confusing. We have automated the entire process, but you can continue with the manual process if you prefer. The following steps describe the automated process:
After you Connect to the Apple Developer Portal, the Upload Certificates screen is displayed:Tip
Prefer the manual way?
Manually upload your certificates from your keychain by clicking on The Manual Way tab.
Follow the guide here if you have any trouble.
Click the clipboard button, to the right of the
curlcommand example. The
curlcommand example is copied to the clipboard.
Open the Terminal application, paste the command into the Terminal window, and press Return.
You should be prompted for a password to access the keychain containing the certificates:
curlscript automatically exports certificates and provisioning profiles that are required for creating signed builds of your app. We’ve already analyzed your project during your first build — and so we only pull what you need to build your project and nothing more.
In your browser, the Code signing is set up! screen is displayed:
Click the Invite testers button to continue with Invite testers to try your iOS app.
When you upload your certificates to buddybuild, your app transitions from using simulator builds to using device builds (a required step before publishing to the App Store). Device builds typically take longer than simulator builds, for several reasons:
If you need faster builds while working on new features or bug fixes, you can disable Build for archive in your app’s build settings. You need to re-enable this setting when you are preparing to deploy to iTunes Connect.
You could also use a branch override setting, so that Build for
archive is only enabled for your
Once the upload is complete, buddybuild has everything it needs to perform device builds. Now all we need is a set of emails to send these builds to — continue with Invite testers to try your iOS app.