Sharing deeplinks to specific TestFlight builds

We use TestFlight to distribute internal development builds for our QA team and internal dogfooders.

Is there any way for us to be able to share a deeplink that would allow internal TestFlight users to install a specific version from TestFlight of our development app?

For instance, right now they have to manually navigate from the the app's screen, to "Versions", then find the marketing version and build number. If we have a lot of folks doing builds around the same time that's a pain. We sometimes see folks install the incorrect build as a result!

While there's the "build groups"s sub tab, it doesn't seem to be ordered in way that makes finding recent builds easy. If I look in there now for instance, I see release candidates from a month ago.

FB13812978

Answered by App Store Connect Engineer in 890515022

Hi there, thank you for your question. We currently don't have a way to generate deeplinks for specific TestFlight versions.

We appreciate you submitting your feedback assistant ticket. You can learn about the latest updates to App Store Connect at:

https://developer.apple.com/news/releases/.

Thanks for reporting the bug.

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert
  Worldwide Developer Relations.

Have ran into this exact problem on SDK teams distributing to multiple partner integrators — same frustration.

No native deep link to a specific build exists today, but two things that actually work:

App Store Connect API

Wire this into your CI pipeline so the moment a build finishes processing, it posts the direct link to Slack or Teams automatically:

GET /v1/builds?filter[app]={appId}&filter[version]={version}&filter[buildNumber]={buildNumber}&filter[processingState]=VALID

Nobody has to navigate anywhere. The link comes to them. Takes about a day to set up and completely eliminates wrong installs.

Named group workaround (works today, zero code)

Create an internal group called "QA-Current". Keep only the active build in it. Share that group link once — when a new build is ready, swap the build in the group. Your QA team always opens the same link, always gets the right build.

Not elegant but it works immediately while waiting for native support.

On the sort order issue in the groups tab — that's a separate problem worth filing independently. Build ordering by recency should be the default for internal groups and it clearly isn't. Your FB13812978 is a good start, but the more individual feedback reports Apple sees on this the better.

What CI system are you using? The API approach is straightforward on Xcode Cloud and GitHub Actions — happy to share the specific implementation if useful. — Divya Ravi, Senior iOS Engineer

Accepted Answer

Hi there, thank you for your question. We currently don't have a way to generate deeplinks for specific TestFlight versions.

We appreciate you submitting your feedback assistant ticket. You can learn about the latest updates to App Store Connect at:

https://developer.apple.com/news/releases/.

Sharing deeplinks to specific TestFlight builds
 
 
Q