Analyze a signed IPA before you share it.

DistKit turns an uploaded IPA into a reviewable Release: package metadata, provisioning details, blocked reasons, history, audience policy, and device follow-up in one place.

Start free Follow the workflow

Package report

Current Release Package-level analysis

Ready for link policy

Info.plistParsed

embedded.mobileprovisionParsed

DistributionAd Hoc

Device ruleRegistered UDIDs

This result describes the package. A specific device may still need to be added to the provisioning profile.

Package checks before sharing.

DistKit parses the package; it does not claim complete cryptographic signature verification.

App identity: Name, version, build number, Bundle ID, minimum OS, and icon when present.
Provisioning: Distribution type, profile name, Team ID, expiry, device count, and Bundle ID match.
OTA result: A package-level ready or blocked result with a concrete reason and next action.

Package report

Current Release Package-level analysis

Blocked

PackageRead successfully

DistributionApp Store

Profile expiryChecked

OTA resultBlocked

The Release stays available for review, but DistKit does not generate a usable OTA path.

App and Release history stay separate.

An App is the durable project. Each upload becomes a Release with its own package report, status, file, and replacement history.

ObjectWhat it keepsPrimary actionStatus

AppBundle ID and current ReleaseOpen release historyActive

Current ReleaseIPA, metadata, provisioning reportCreate audience linkDistributable

Blocked ReleasePackage report and blocked reasonUpload corrected IPANeeds action

Set access rules for each tester link.

Different audiences can point to the same Release without sharing one password or one lifecycle.

PolicyWhat DistKit checksOutcome

PasswordUnlock session before the manifest requestUnauthorized requests stop

ExpiryCurrent time against link expiryExpired link stops serving

Request limitAuthorized manifest requests against the limitFurther requests stop

Enabled statePublisher-controlled link statusFurther requests stop once the link is disabled

A manifest request is an install-attempt signal. It does not confirm that iOS completed installation.

Device follow-up stays explicit.

For Development and Ad Hoc packages, the tester device must be included in the provisioning profile.

1
Tester collects the UDID through the explicit device-profile flow.
2
Release owner registers it in Apple Developer and updates the profile.
3
Owner re-exports the signed IPA and replaces the Release.

Package report, not a device guarantee.

DistKit shows what can be read from the IPA and provisioning profile. It cannot query Apple Developer for every tester or confirm the final iOS installation state.

Read product answers

Keep every build reviewable.

Start with the package report, then publish only the Release and audience policy you intend.

Start free Follow the workflow