Do I need to expire the current build in TestFlight in order for a group to get the new one?

Question

Created Jun ’17

Replies 1

Boosts 0

Views 4.1k

Participants 1

I created a group of testers in TestFlight and added a build to this group. Each member of the group received the invitation and started testing. All good.

I then got an updated the version of the build approved, which I added to the same group.

- What does this do? Do the testers of this group receive a new invitation to install the new build?

- If they open the Testflight app, do they see the two builds? Only the last one?

Clicking on this group on the web, and then selecting the "Builds" tab on TestFligh web shows the two builds:

- The latest one is in "Ready to Test" state

- The previous one is in "Testing" state

This then suggest that the latest build has not been distributed to the testers.

Do I need to expire the previous build in order for them to get the current one?

If so, what is the purpose of enabling multiple builds per group?

I'd appreciate any clarifications you guys may have. I wish Apple was less vague about all this in its documentation.

Thanks!

Boost

Answer 1

luannguyen OP

Jun ’17

Accepted Answer

Here's an update of my finding to people who are experiencing the same issue.

I called the support helpline, they explained that what I want to do is not feasible in TestFlight.

If you have multiple builds of the same app added to the same external tester group, you first need to expire the previous version of the build in order for your testers to get the new one.

This means that, if you need to push the latest build of your app to any new testers, but do not want to force your current testers to install the new build because your updates are not significant and they should not be bothered (e.g., some investors or executives), you need to create a separate group for the new testers.

Not ideal, but at least workaround-able.

1