Inviting Testers

Now that we have a green build of your app, the next step is to deploy it to your testers.

But before we do that, buddybuild requires your Code Signing Identities and Provisioning Profiles to create signed device builds.

The Invite testers screen

Step 1: Upload Certificates

Finding and uploading specific items from your keychain can be painful and confusing. We have automated this entire process. Upon completing a successful build, you’ll be prompted to upload certificates using the buddybuild Cert-Uploader tool.

Simply copy the curl line in the page and paste it into your terminal.

The Upload Certificates screen

This curl script 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.

Cert-Uploader output


Prefer the manual way?

Manually upload your certificates from your keychain by clicking on The Manual Way.

Follow the guide here if you have any trouble.

Once the upload is complete, buddybuild will have everything it needs to perform device builds. Now all we need is a set of emails to send these builds to — which brings us to the next step!

The Apple Developer Portal Synced screen


When you upload your certificates to buddybuild, your app transitions from using simulator builds to using device builds. Device builds typically take longer than simulator builds, for several reasons:

  • Code signing

  • Provisioning profile management

  • dSYM management

  • Deployment (not possible for simulator builds)

  • Archive builds (multiple architectures, bitcode, plus additional iTunes Connect requirements).

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 master branch; development branches would use simulator builds, and only your master branch would use a device build.

Step 2: Invite Testers

Here you can create groups you would like to send builds to. We’ve already created a default group with your email in it.

Feel free to add more groups and emails in whatever configuration you want.

You can also configure deployment frequencies and branch targets specific to each group. These options allow you to fine tune who gets which build and how often.

The Invite Testers screen

Once you’re done configuring your groups, click the Invite Testers button. We’ll spin up a device build and email it to the groups you’ve specified.


Wondering what your testers receive?

Follow the Tester’s Manual to see their experience.

That’s it! Now that we have device builds going out to your testers, you’ll now want a way to solicit feedback from them.

The buddybuild SDK’s Feedback Visual Reporter makes this process very simple. Proceed to the next step to integrate the buddybuild SDK into your app.

results matching ""

    No results matching ""