Publishing on TestFlight, new testers, do I really need to rebuild / load profile profiles?

Question

I published the application through the testflight website to allow my colleagues to check, and as more and more of them open their original email address and find time to go through the registration process, testers leak into my testflight team.

However, the process of adding them to the test seems a bit confusing, so I decided to check and ask if I was doing it right, or if I missed something obvious.

At the moment, the whole procedure looks like this:

• A colleague opens an original letter with a link to an invitation
• Then it registers the device and registers for testing
• I was informed about this new test via email and through the testflight website.
• Then I need to download (or write / copy) the UDID list of all new testers from the last time
• Then I need to visit part of the device on the Apple Developers website and download this file
• Edit the provisioning profile to enable new devices.
• Wait for it to approve and upload the preparation profile
• I drag the provisioning profile into the Xcode provisioning profile organizer.
• Then I go back to MonoDevelop and guarantee that it still points to the correct profile (I don’t know if using MonoDevelop / MonoTouch complicates this process, so I didn’t want to leave it, it may not be relevant for this question)
• I rebuild and republish testflight
• Then I visit the testflight website, find a new / updated build and guarantee that all my testers will be informed about this.

I noticed that if I do not update the version, it will "silently" replace the existing assembly and reuse the list of testers that have already been informed, so if I just check all the new testers and finish, we only inform the new ones.

However, it seems that some work should be related to downloading and disabling preparation profile files.

Am I missing something obvious? Is there any way to ease me some of this?

For example, I noticed that I can create a provisioning profile inside the Xcode organizer, however this dialog box does not display any certificates, so I cannot complete this dialog box. If this is a key element, leave a short answer to this effect, and I will instead post a new question about it.

This question is true: Is this procedure correct?

Answer 1

Yes, you need to go through this manual process to add a UDID to your profile. Unfortunately, unfortunately not.

After creating a new position, you can use xcode to "synchronize" the new rule file if you want. Open it, go to the "Organizer", select "Preparation profiles" on the left and click "Update." I honestly do it manually, it is not much work.

Answer 2

No need to rebuild .ipa

• Download .ipa
• Send invitations to testers
• Add your devices to the provisioning profile
• Download Approved Profile
• Go to TestFlight assembly → Permissions → Download profile ...
• Click "Send Email / Update"
• You are done - the new user received a link to download the application.

Hope this helps.

Answer 3

Testflight has the ability to update the preparation file in a couple of months. Before he was already there, but the Area 51 features should be viewable. Thus, steps 8, 9, and 10 are no longer needed.

Answer 4

I have done quite a bit of work for Ad-Hoc applications on iOS and that the Apple procedure forces you to accept if you do not fail to subscribe to the Enterprise account.

Answer 5

TestFlight allows you to download a new training profile, so you did not have to rebuild to add new testers. TestFlight will then re-sign your existing applications and inform the appropriate users. But it seems that after the release of Xcode 6, they chose this option. Perhaps something is related to the new way of signing applications.

https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205