DistKit
Sign in Start free
Menu
Sign in Start free

From signed IPA to tester.

One ordered path connects package analysis, Release policy, a tester’s manifest request, and the Apple Developer work required when a device is not yet eligible.

Start free Review product details
  1. 01Upload an already-signed IPA
  2. 02Read the package report
  3. 03Choose a Release and audience
  4. 04Share the tester page
  5. 05Resolve device eligibility if needed

The complete distribution path.

Each step ends with a visible decision or owner; nothing here implies that DistKit changes the IPA.

  1. 01

    Upload an already-signed IPA

    Export the build with Xcode or your existing pipeline. DistKit does not sign, re-sign, or modify the package.

  2. 02

    Read the package report

    DistKit parses Info.plist and embedded.mobileprovision to surface version, Bundle ID, distribution type, profile expiry, and device rules.

    ReadyContinue to Release policyBlockedKeep report and upload a corrected IPA
  3. 03

    Choose a Release and audience

    Keep the build in its App history, then create a link with a password, expiry date, manifest-request limit, and enabled state.

  4. 04

    Share the tester page

    The tester opens the Release page in Safari and requests the iOS installation manifest. A DistKit account is not required for the tester.

  5. 05

    Resolve device eligibility if needed

    For Development or Ad Hoc builds, collect the UDID, register it in Apple Developer, regenerate the profile, re-export the IPA, and upload the replacement.

If the tester device is not in the profile.

DistKit can collect the UDID, but the Release owner completes the Apple-side registration and signs the replacement build.

TesterReturn device UDID

Explicit temporary-profile flow; no MDM enrollment.

Release ownerRegister and update

Add the device in Apple Developer and regenerate the provisioning profile.

Xcode or CIRe-sign and export

Create a new IPA that includes the updated provisioning profile.

DistKitReplace the Release

Run the package report again before sharing.

What DistKit can measure

Release-page activity and authorized manifest requests can show that a tester reached the installation handoff.

What the web cannot confirm

DistKit cannot confirm that iOS downloaded the whole IPA, completed installation, launched the app, or that every device was eligible.

Apple owns device eligibility.

Use Apple’s current documentation when registering devices and creating an Ad Hoc provisioning profile.

Apple: distribute to registered devicesApple: create an Ad Hoc provisioning profile

Publish only the intended Release.

Review the package, set the audience policy, and use the device branch only when the provisioning profile requires it.

Start free Read the FAQ