Using TestFlight to Install Builds

How to share iOS builds through TestFlight

Doris Sooläte avatar
Written by Doris Sooläte
Updated over a week ago

A very common way of sharing iOS builds is through TestFlight. The following information assumes that the user has already installed the TestFlight app on their mobile device.

Remember that, in accordance with the Freelancer Services agreement, builds (including access links and metadata) are confidential information and you must not disclose them to any third party.

Installing a build using a Testlio shared test AppleID

A shared AppleID usually means that Testlio has provided a client an AppleID that client has shared their app to. Testlio will use the same AppleID to make the app available to our testers. Why we use this option is that sending our testers personal AppleIDs would be a time consuming effort for all parties involved.


  1. Open the TestFlight app.

    • Make sure you have logged out from your personal account or any other project shared test accounts.

  2. Log in using the shared AppleID provided by Testlio.

    • It could be shared in ‘Instructions to testers’ section or Rocket.Chat.

  3. Apple wants to force use of two-factor authentication (2FA), but we do not want to use that. Following the guide will help you not to do that - when you’re prompted for this, please select ‘Don’t upgrade’.

Activities after you have completed testing

  1. You always must log out after testing.

Installing a build using a public link

When a public link is used, that means that testers can use their own AppleIDs to sign up for testing since the invite link is public.


  1. Click the public link shared in the run instructions.

    • Example public link:

  2. TestFlight app open.

  3. Follow instructions provided and install the app.

  4. Start testing.

  5. After ending the test, remove your AppleID from testing.

Remove your AppleID from testing

To remove your AppleID, follow these steps.

  1. Open TestFlight.

  2. Open the app and scroll to the bottom of the page.

  3. Click ‘Stop testing’.


Did this answer your question?