Most of the time there is an error displayed detailing the issue that has occurred.
Some of the errors that are displayed relate to the following issues that TestFlight will detect with a build:
- The build is not signed with an ad hoc or enterprise distribution provisioning profile
- The build is having a conflict with it's provisioning profile (usually related to mismatched keychain access)
- The provisioning profile does not contain provisioned devices (ie. no UDIDs are associated in the build, often occurring if you upload a build that has been signed for the App Store and not ad hoc)
- There is an issue with the application's entitlements
- An unexpected error, usually related to an issue with a build TestFlight has not seen before or something is wrong with the validation of builds
TestFlight follows Apple's beta and internal distribution guidelines and apps that are prepared this way should not have a problem being uploaded and validated.
You can learn more about preparing a build for distribution with TestFlight here.
The links below offer some more in-depth explanations on some of the errors you may encounter:
- "Invalid IPA: does not contained provisioned devices"
- Mismatched keychain-access-groups
- Mismatched ubiquity.kvstore-identifier value
- Invalid Profile: distribution build entitlements must have get-task-allow set to false.
If you do experience an error on upload and are not sure how to fix it, please contact us here, and include a screenshot of the error and the .IPA so that we may be able to troubleshoot the error.
If you are experiencing an error when using the desktop app, please see the article here.