Analyze a signed IPA or APK before sharing.

DistKit turns an uploaded mobile package into a reviewable Release with identity, version, signing context, history, audience policy, and a platform-specific installation handoff.

Start free Follow the workflow

Package report

Current Release Package-level analysis

Ready for link policy

PackageIPA or APK

App IDDetected

VersionParsed

DeliveryPlatform aware

This result describes the package. The target device still applies its platform installation rules.

Package checks before sharing.

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

App identity: Name, version, build number, Bundle ID or Application ID, minimum OS or SDK, and icon when present.
iOS provisioning: Distribution type, profile name, Team ID, expiry, device count, and Bundle ID match.
Android package: Installable APK status, target SDK, available signing information, and direct-download readiness.

Package report

Current Release Package-level analysis

Blocked

PackageRead successfully

Platform rulesChecked

Signing statusNeeds action

Delivery resultBlocked

The Release stays available for review, but package delivery remains blocked until corrected.

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

AppPlatform, App ID, and current ReleaseOpen release historyActive

Current ReleaseIPA or APK, metadata, package reportCreate audience linkDistributable

Blocked ReleasePackage report and blocked reasonUpload corrected packageNeeds 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 package deliveryUnauthorized requests stop

ExpiryCurrent time against link expiryExpired link stops serving

Download limitAuthorized installation handoffs against the limitFurther requests stop

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

An iOS manifest handoff or Android APK download is an attempt signal. It does not confirm installation or first launch.

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