AppForShareCreate a free account

One tester list for AppForShare links and TestFlight

Team

Many teams test Android builds with install links and iPhone builds in TestFlight, so the same people live in two lists that drift apart. Link an AppForShare tester group to an external TestFlight group and it stays the one list.

Example

Client QA, linked to TestFlight

Made for

  • Teams that ship to TestFlight and want the client or QA list kept in one place
  • Agencies that add and remove client testers often

What it ends

  • Adding the same tester in AppForShare and again in App Store Connect
  • Former testers who keep TestFlight access for months
  • Not knowing which testers accepted the TestFlight invite

How it works

  1. Step 1

    Link the group

    On the project's Testing page, link a tester group to a new or existing external TestFlight group of a shared Apple app.

  2. Step 2

    Members sync

    New members are added with email and name within about a minute. Members who leave are taken out again, but only the ones AppForShare added.

  3. Step 3

    See Apple's status

    Each tester shows waiting for a build, invited, accepted, installed or access removed, as Apple reports it.

Builds and beta review stay with you

A person gives a processed build to the group and submits it for TestFlight beta review; AppForShare never does that on its own. Apple sends its own invite email once the group has a build. Stopping the sync leaves the TestFlight group and its testers as they are.

Good to know

Questions

Which key role does it need?
A key that can manage testers, such as App Manager.
Can I see what was changed in TestFlight?
Yes. Every call is in the connection's activity log, including automatic adds and removals, under the person who linked the group.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

More features