I have published an app through the testflight website to allow my colleagues to test, and as more and more of them opens the initial email and find time to go through the registration process, testers are trickling in on my testflight team.
However, the process to add them to the test seems a bit convoluted, so I thought I'd verify, and ask, if I'm doing it right, or if I have missed something obvious.
At the moment the whole procedure looks like this:
- A colleague opens up the initial email, with the invitation link
- He/she then registers the device, and registers for the test
- I am informed of this new tester through an email and through the testflight site
- I then have to download (or write down/copy) the list of UDID's of all the new testers since last time
- I then have to visit the devices part of the Apple Developers site, and upload that file
- Edit my provisioning profile to include the new devices
- Wait for it to approve, and download the provisioning profile
- I drag the provisioning profile into the Xcode provisioning profile organizer
- I then go back to MonoDevelop, and ensure it is still pointing to the right profile (I don't know if using MonoDevelop/MonoTouch complicates this process so I didn't want to leave it out, it might be irrelevant for this question)
- I rebuild, and republish on testflight
- I then visit the testflight website, find the new/updated build, and ensure all my testers are informed of it
I noticed that if I do not update the version, it will "silently" replace the existing build, and reuse the list of testers that have already been informed, so if I just check all the new testers and complete, it'll only inform the new ones.
However, it seems a bit of a work to have to keep downloading and mucking about with the provisioning profile files.
Did I miss something obvious? Is there a way