iOS apps

How iOS over-the-air installation works

How Apple's itms-services protocol, signed XML manifests, and embedded provisioning profiles install .ipa builds wirelessly.

The itms-services:// wireless handshake

Unlike Android devices (which install .apk files downloaded directly by the browser), iOS and iPadOS install non-App-Store builds through Apple's native itms-services OTA protocol:

  1. The tester opens /i/{hash} in Apple Safari and taps Install application.
  2. Safari triggers an itms-services://?action=download-manifest&url=… URL pointing to a short-lived, cryptographically signed manifest.plist endpoint on BuildDrop.
  3. The iOS background daemon (itunesstored) fetches manifest.plist—without sharing Safari's browser cookies—and reads the software-package HTTPS URL, bundle identifier, version, and app icons.
  4. itunesstored streams the .ipa archive over HTTPS, verifies Apple's code signature and embedded.mobileprovision, and places the app icon onto the Home Screen with a live progress ring.

Why BuildDrop never re-signs your .ipa

BuildDrop streams your uploaded .ipa byte-for-byte without altering its signature or entitlements. Push notifications, CarPlay, Keychain groups, App Groups, and Associated Domains behave identically to a build installed over USB from Xcode.