Permissions & distribution. When a build is uploaded to TestFlight, it will first recognize that the uploaded file is a valid IPA and will read the provisioning profile embedded in the IPA to determine which devices can install the build and in turn which users.
This information is displayed on this page: This page (known as the build's permission page) is the central terminal for distributing a build in TestFlight. From here you can see which team members has a provisioned device, other people not currently on your team are included in the provisioning profile, anonymous devices associated with the build, and team members who do not have a provisioned device.
TestFlight users and devices on this page need to be selected to be able to download and install the build on their device. When you select a user(s) to receive a build you have the option to 'Just Update' who has access or 'Update & Notify'. Adding more testers to a build? If you've already distributed a build and have had a few more teammates join your team since it was distributed, how do you get them the latest build?
The general process is as follows: The new team members devices will need to be added to the Apple Developer portal associated with your Apple developer account. Upload a build? Create an IPA (Xcode 4.3) With the release of Xcode 4.3, Apple has made it even easier to generate an IPA.
However, some of these changes have caused some confusion with some users. This tutorial will walk you through the easiest way to generate an IPA as well as some more advanced configurations. We will be using a sample project which will walkthrough creating the project to IPA generation. NOTE: this tutorial only covers how to configure your project in order to package the application as an IPA.