DEV Community: Kaushal Rola

How to Distribute iOS Apps Without TestFlight

Kaushal Rola — Mon, 03 Aug 2026 17:35:30 +0000

Originally published on the BetaDrop blog.

TestFlight isn't always the answer. Apple's official beta testing platform has its limitations—24-hour review times, 90-day build expirations, and the requirement for testers to install yet another app. If you're looking for faster, more flexible iOS app distribution, you have options.

This guide covers everything you need to know about distributing iOS apps without TestFlight. We'll explore Over-The-Air (OTA) distribution, the technical requirements, and practical solutions that work in 2026.

Why Skip TestFlight for iOS Distribution?

TestFlight is excellent for public beta testing, but it's not always the right fit. Here's when you might want alternatives:

Speed matters — TestFlight reviews can take 24-48 hours. OTA distribution is instant.
Internal builds — Sharing quick iterations with your team shouldn't require Apple approval.
No app installs for testers — Your testers don't need to download TestFlight.
Build lifespan — TestFlight builds expire after 90 days. OTA links can last indefinitely.
Privacy concerns — Some teams prefer not to route builds through Apple's servers.

Understanding iOS OTA Distribution

Over-The-Air (OTA) distribution uses Apple's itms-services protocol. When a user taps an installation link, iOS reads a manifest.plist file that points to your IPA. The device downloads and installs the app directly—no computer needed.

The technical flow works like this:

User taps a special itms-services:// link on their iOS device
iOS fetches the manifest.plist file from your HTTPS server
The manifest contains your app's metadata and IPA download URL
iOS downloads the IPA and prompts the user to install

Requirements for OTA Distribution

1. A Signed IPA File

Your IPA must be signed with either an Ad Hoc or Enterprise provisioning profile. Development profiles won't work for OTA installation.

Ad Hoc — Allows up to 100 devices per device type. Each device UDID must be registered in your Apple Developer account.
Enterprise — Unlimited devices but requires a $299/year Apple Developer Enterprise Program membership.

2. HTTPS Hosting

Apple requires that both your manifest.plist and IPA file are served over HTTPS. This isn't optional—HTTP links simply won't work. You'll need valid SSL certificates on your hosting server.

3. Manifest.plist File

The manifest file tells iOS where to find your app and provides essential metadata:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>items</key>
  <array>
    <dict>
      <key>assets</key>
      <array>
        <dict>
          <key>kind</key>
          <string>software-package</string>
          <key>url</key>
          <string>https://yourserver.com/app.ipa</string>
        </dict>
      </array>
      <key>metadata</key>
      <dict>
        <key>bundle-identifier</key>
        <string>com.yourcompany.app</string>
        <key>bundle-version</key>
        <string>1.0.0</string>
        <key>kind</key>
        <string>software</string>
        <key>title</key>
        <string>Your App Name</string>
      </dict>
    </dict>
  </array>
</dict>
</plist>

Method 1: Manual OTA Setup

You can set up OTA distribution yourself with any web server. Here's the process:

Export your IPA from Xcode with Ad Hoc or Enterprise distribution
Upload the IPA to your HTTPS server
Create the manifest.plist with your app details
Upload the manifest.plist to your server
Create an install link: itms-services://?action=download-manifest&url=https://yourserver.com/manifest.plist

The downside? This is tedious for every build, error-prone, and requires server maintenance.

Method 2: Automate OTA With a Hosting Service

BetaDrop automates the entire OTA process. Upload your IPA, and we generate the manifest, host everything over HTTPS, and give you a shareable link—instantly.

Here's how it works:

Drag and drop your IPA file to BetaDrop
We extract app metadata automatically
Get your install link in seconds
Share with testers via any channel

No server setup. No manifest files to maintain. No HTTPS certificates to manage. Just upload and share.

Registering Device UDIDs

For Ad Hoc distribution, tester devices must be registered in your Apple Developer account. Here's how to get a device UDID:

On Mac — Connect the device, open Finder, click the device, and click the serial number until UDID appears
On the device — Use a UDID lookup website or app
Via BetaDrop — send testers the free UDID checker to read off their device UDID

Once you have UDIDs, add them in the Apple Developer portal under Devices, then regenerate your provisioning profile.

Common OTA Installation Issues

Unable to Install Error

This usually means the device isn't registered in your provisioning profile (for Ad Hoc) or your IPA isn't properly signed.

Untrusted Developer

For Enterprise and some Ad Hoc builds, users need to trust your developer certificate. Go to Settings → General → VPN & Device Management → tap your certificate → Trust.

Link Opens Safari Instead of Installing

The itms-services:// link must be opened on Safari or another iOS browser. Some apps (like Slack) open links in embedded browsers that don't handle this protocol.

Frequently Asked Questions

Can I distribute iOS apps without TestFlight?

Yes. Over-The-Air (OTA) distribution using the itms-services protocol is Apple's supported method for distributing apps outside TestFlight and the App Store.

What do I need to distribute iOS apps without TestFlight?

You need an IPA signed with Ad Hoc or Enterprise provisioning, HTTPS hosting, a properly formatted manifest.plist, and registered device UDIDs (for Ad Hoc).

Is OTA distribution legal for iOS apps?

Absolutely. Apple explicitly provides the itms-services protocol for this purpose. It's the standard method for enterprise apps and internal beta testing.

How many testers can I have without TestFlight?

Ad Hoc distribution allows 100 devices per device type annually. Enterprise distribution has no device limits but requires the Enterprise Program membership.

Do testers need to install anything?

No additional apps required. Testers just tap the install link on their iOS device. They may need to trust your developer certificate the first time.

Summary

Distributing iOS apps without TestFlight is straightforward with OTA distribution. Whether you set it up manually or use a platform like BetaDrop, you can bypass TestFlight's limitations and get builds to testers instantly.

The key requirements are:

A properly signed IPA (Ad Hoc or Enterprise)
HTTPS hosting for your files
A valid manifest.plist
Registered device UDIDs (for Ad Hoc)

For the fastest workflow, upload your iOS IPA on BetaDrop and get a shareable install link in seconds—no server setup required.

How do you get iOS builds to testers without waiting on TestFlight review — Ad Hoc OTA, Enterprise, or something else? Curious what's actually worked for you.

Best Free Beta App Distribution Platform (2026)

Kaushal Rola — Mon, 03 Aug 2026 17:35:19 +0000

Originally published on the BetaDrop blog.

Choosing a beta distribution platform shouldn't break your budget. Whether you're an indie developer testing your first app or a startup iterating rapidly, you need a reliable way to get builds into testers' hands without paying enterprise prices.

This guide compares the best free beta app distribution platforms in 2026. We'll cover features, limitations, and help you pick the right tool for your workflow.

What to Look for in a Beta Distribution Platform

Before diving into specific platforms, here's what matters most:

Platform support — Does it handle both iOS and Android?
Speed — How fast can you get builds to testers?
Tester experience — Do testers need accounts or app installs?
Upload limits — Are there restrictions on file sizes or number of builds?
Pricing transparency — Is it truly free or limited trial?
Privacy — Where is your app binary stored?

Top Free Beta Distribution Platforms Compared

1. BetaDrop — Best for Speed and Simplicity

BetaDrop is a free, no-account-required beta distribution platform. You can upload iOS IPA or Android APK files and get a shareable install link instantly.

Key features:

Truly free — no paid tiers, no hidden fees
iOS OTA installation without TestFlight
No tester registration required
Instant link generation
Upload limits: 512MB for both IPA and APK
QR codes for easy mobile sharing

Best for: Developers who want the fastest possible distribution with minimal setup. Ideal for quick internal testing and prototype sharing.

2. Firebase App Distribution — Best for Firebase Users

Google's Firebase App Distribution integrates with the Firebase ecosystem. It's free and supports both iOS and Android.

Key features:

Tight integration with Firebase services
Gradle and Fastlane plugins
Tester groups management
Crash reporting integration
Pre-release app sharing

Limitations:

Testers need Firebase App Tester app (iOS) or email invitation
Requires Google account or email signup for testers
More setup required compared to simpler alternatives

Best for: Teams already using Firebase who want unified tooling.

3. TestFlight — Apple's Official iOS Solution

TestFlight is Apple's built-in beta testing platform for iOS apps. It's free and widely used.

Key features:

Native iOS integration
Up to 10,000 external testers
Automatic crash reports
Tester feedback within the app

Limitations:

iOS only — no Android support
24-48 hour review for external testing
Builds expire after 90 days
Testers must install TestFlight app
Requires Apple ID for testers

Best for: Public beta testing with many external testers on iOS. Check our guide on TestFlight alternatives if the limitations are a problem.

4. Diawi — Quick Upload Solution

Diawi offers quick IPA and APK distribution through a simple web interface.

Key features:

Simple drag-and-drop upload
No account required for basic use
Password protection option
Both iOS and Android support

Limitations:

Free tier has stricter limits
Links expire (free tier: few days)
Download statistics require paid plan
No tester management

Best for: One-off quick shares when you don't need persistence.

5. Microsoft App Center — Enterprise Features

App Center provides distribution alongside CI/CD, analytics, and crash reporting.

Key features:

Full CI/CD pipeline
Automatic builds from repos
Both platforms supported
Detailed analytics
Distribution groups

Limitations:

Complex setup for distribution-only use
Build hours limited on free tier
Overkill if you just need distribution

Best for: Teams wanting integrated DevOps tooling.

Platform Comparison Table

Platform	iOS	Android	Tester Account	Review Time	Truly Free
BetaDrop	✓	✓	Not required	Instant	Yes
Firebase	✓	✓	Required	Instant	Yes*
TestFlight	✓	✗	Required	24-48h	Yes
Diawi	✓	✓	Not required	Instant	Limited
App Center	✓	✓	Required	Instant	Limited

*Firebase is free but within the broader Firebase/Google Cloud ecosystem

Choosing the Right Platform

For Solo Developers

Go with BetaDrop or Diawi for minimal setup. You don't need complex tester management—just upload and share links.

For Small Teams / Startups

BetaDrop works great for rapid iteration. If you're already on Firebase, their distribution tool integrates well. Check our guide on internal app distribution for startups.

For Large Organizations

App Center or Firebase offer the management features you'll need. Consider TestFlight for iOS public betas with large tester pools.

Frequently Asked Questions

What is the best free beta app distribution platform?

For most developers, BetaDrop offers the best combination of simplicity, speed, and truly free pricing. Firebase is excellent if you're already in that ecosystem.

Are there free alternatives to TestFlight?

Yes. BetaDrop, Firebase App Distribution, and Diawi all offer free iOS distribution without TestFlight's review delays.

Do beta distribution platforms require testers to create accounts?

Not all. BetaDrop and Diawi don't require tester accounts. Firebase and TestFlight do require authentication.

Can I distribute both iOS and Android apps with one platform?

Yes. BetaDrop, Firebase, Diawi, and App Center all support cross-platform distribution.

Which platform is fastest for getting builds to testers?

BetaDrop provides instant links after upload. No review process, no tester invitations needed.

Summary

The best free beta distribution platform depends on your needs:

Fastest and simplest: BetaDrop — upload and share in seconds
Firebase users: Firebase App Distribution — integrated ecosystem
iOS public beta: TestFlight — large tester pools, built-in feedback
Full DevOps: App Center — CI/CD plus distribution

If you want to skip the setup and start distributing now, upload your build on BetaDrop and get a shareable link instantly.

Which free distribution tool are you using in 2026, and what made you pick it? Anything you wish it did better?

7 Best Mobile App Beta Testing Tools (2026)

Kaushal Rola — Mon, 03 Aug 2026 17:34:40 +0000

Originally published on the BetaDrop blog.

The best mobile beta testing tools in 2026 are TestFlight and Google Play Console for final release candidates, with Firebase App Distribution and BetaDrop as the top picks for fast nightly internal builds. For the best free option, Firebase App Distribution and BetaDrop both distribute iOS and Android builds at no cost — BetaDrop adds instant over-the-air install links with QR codes and needs no tester accounts, while Firebase runs through its console and SDK. AppCenter, Diawi, and TestFairy round out the seven tools compared below.

Getting your app into the hands of real users is the only way to find bugs before launch. But email attachments don't work for apps. You need a platform.

Here are the top 7 tools for mobile beta distribution in 2026.

1. TestFlight (iOS only)

The gold standard for iOS.

Pros: Built into iOS. Easy to install. No UDID management for external testers. Supports up to 10,000 external testers.

Cons: iOS only. Requires a paid Apple Developer Program membership ($99/year). External builds must clear Beta App Review before testers can install, and every build expires after 90 days.

Internal testers (App Store Connect users on your team) skip review and can install immediately, so keep external groups for wider betas only. If the review wait is the blocker, see our TestFlight alternative for instant OTA installs.

2. Google Play Console (Android only)

The official way for Android.

Pros: Seamless transition to production. Auto-updates. Internal testing track reaches up to 100 testers with no review.

Cons: Testers need a Google account and must opt in via a link before they can download. Requires a one-time $25 developer registration, and closed/open tracks can be slow to process builds.

3. Firebase App Distribution

Google's cross-platform tool.

Pros: Fast. Free. Works for both iOS and Android. Great CLI integration.

Cons: For iOS, you still need to manage provisioning profiles (UDIDs).

Distribution runs from the Firebase CLI, for example firebase appdistribution:distribute app.ipa --app <APP_ID> --groups testers. That is fast on Android, but every new iOS tester still means collecting a UDID, adding it in the Apple Developer portal, and re-signing. See our Firebase App Distribution alternative if the UDID churn is slowing you down.

4. BetaDrop

A free, no-account alternative focused on speed.

Pros: Upload an .ipa or .apk (up to 512 MB) and get an instant over-the-air install link plus a QR code. Testers install straight from their phone browser — no TestFlight, no App Store or Play Store, no tester accounts, no cables, no review wait. Ships a terminal CLI (npm i -g @betadrop/cli) and an MCP server for AI coding agents.

Cons: Builds are ephemeral — registered builds expire within about 30 days and anonymous guest links after 24 hours — so it is built for active testing, not permanent hosting.

To try it, upload your iOS IPA and share the link or QR code that comes back seconds later.

5. AppCenter (Microsoft)

Formerly HockeyApp.

Pros: Enterprise-grade. Good for huge teams.

Cons: Microsoft has announced App Center is being retired, so it is no longer a safe long-term bet. Read our App Center alternative before you migrate a pipeline onto it.

6. Diawi

The classic "drag and drop" tool.

Pros: incredibly simple for one-off shares. Still needs registered UDIDs for Ad Hoc iOS builds.

Cons: Links expire quickly on the free plan, and free uploads are throttled. Our Diawi alternative keeps the drag-and-drop simplicity without the paid-tier gate.

7. TestFairy

Focused on recording sessions.

Pros: Videos of what users did before the crash.

Cons: Can be expensive.

Verdict

Use TestFlight and Play Console for your final release candidates. Use Firebase or BetaDrop for your nightly internal builds where speed matters.

When BetaDrop is the right call

If your bottleneck is the Beta App Review wait or tester accounts, BetaDrop is the fastest way out. It is free, handles both iOS and Android, and turns a build into an over-the-air install link and QR code with no account for you or your testers. Reach for it for same-day internal builds and bug-fix verification, then graduate the polished release candidate to TestFlight or Play Console. Start by uploading an IPA, and if you are weighing the trade-offs, compare it directly as a TestFlight alternative or Diawi alternative.

Frequently Asked Questions

Is TestFlight free?

TestFlight itself is free, but it requires a paid Apple Developer Program membership ($99/year). Internal testers can install builds without Beta App Review, while external testing (up to 10,000 testers) must pass Apple's review first.

Can I use Firebase App Distribution for iOS?

Yes. Firebase App Distribution supports both iOS and Android for free, but iOS builds are Ad Hoc, so you must register each tester's device UDID in your Apple Developer account and re-sign the build before every distribution.

What is the fastest way to send a beta build to a tester?

Upload the .ipa or .apk to BetaDrop and share the generated over-the-air install link or QR code. The tester opens it in their phone browser and installs directly — no TestFlight, no App Store or Play Store, no tester account, and no review wait.

Which mobile beta testing tools are free?

Firebase App Distribution and BetaDrop are both free for iOS and Android. TestFlight and Google Play Console require the paid developer accounts ($99/year for Apple, a one-time $25 for Google Play). Diawi and TestFairy are paid once you pass their free-tier limits.

Do beta testers need an account to install a build?

It depends on the tool. TestFlight requires testers to install the TestFlight app and sign in with an Apple ID, and Google Play Console requires a Google account. With BetaDrop, testers need no account at all — they just tap the install link.

How large a build can I upload, and how long does the link last?

BetaDrop accepts builds up to 512 MB. Registered builds expire within about 30 days, and anonymous guest links expire after 24 hours, so BetaDrop is built for active testing cycles rather than permanent hosting.

Which of these seven do you actually reach for day to day — and for which part of the cycle, nightly internal builds vs release candidates? Curious what your stack looks like.

How to Overcome TestFlight User Limits

Kaushal Rola — Mon, 03 Aug 2026 17:34:23 +0000

Originally published on the BetaDrop blog.

Apple's TestFlight is the gold standard for iOS beta testing. It's built right into the ecosystem and easy for users. But it has a hard ceiling: 10,000 external testers.

For most apps, this is plenty. But for viral hits or large-scale open betas, hitting this wall can stop your momentum cold. Here is how to manage and overcome these limits.

Understanding the Limits

Internal Testers: Max 100. No Beta App Review required, and builds appear almost immediately. Each internal tester must be a member of your App Store Connect team and can install on up to 30 devices.
External Testers: Max 10,000 per app. Invited by email or a Public Link. The first build of each new version must clear Beta App Review before external testers can install it.

The 10,000 ceiling is per app (Bundle ID), not per group. You can split external testers across up to 100 groups, but every group draws from the same 10,000-slot pool. If you only need to hand a build to a handful of QA folks or a client, an OTA install link sidesteps the review wait entirely.

Strategy 1: Pruning Inactive Testers

The 10k limit is for active slots, not lifetime adds. Many users install a beta and never open it again. You should aggressively prune these users to make room for fresh testers.

How to prune:

Go to App Store Connect → TestFlight.
Select your External Group.
Sort by Status or Sessions.
Select users who haven't installed or have 0 sessions in 30 days.
Click Delete.

Pro Tip: You can automate this using fastlane pilot scripts to remove testers who haven't launched the latest build.

Strategy 2: Use Enterprise Distribution

If your goal is to test internally with a massive organization (e.g., a company with 50,000 employees), TestFlight isn't the right tool. Use the Apple Developer Enterprise Program.

This allows unlimited distribution to devices owned by your organization, bypassing the 10,000 user limit entirely.

Strategy 3: Apple Business Manager (Custom Apps)

For B2B apps where you are distributing to specific partners or clients, use Apple Business Manager. This allows you to privately distribute specific apps to another organization's VPP (Volume Purchase Program) account. The receiving organization then distributes the app to their users via MDM.

Strategy 4: "Rolling" Betas

If you have a waiting list, create a "churn" system. Invite 1,000 users, give them 2 weeks to test, and then remove them to invite the next 1,000. This keeps feedback fresh and allows you to test with far more than 10k unique users over time.

The "Nuclear Option": Multiple App IDs

Technically, the limit is per App ID (Bundle ID). You could create com.app.beta1, com.app.beta2, etc., each with its own TestFlight group.

Warning: This separates your analytics, crash reports, and requires managing multiple app records. It is messy and generally not recommended unless absolutely necessary.

Skip the Cap With OTA Links

If tester counts are the real bottleneck, you don't have to fight the 10,000-slot math at all. BetaDrop is a free TestFlight alternative: upload a signed .ipa and you get an instant over-the-air install link plus a QR code with no tester cap, no tester accounts, and no Beta App Review. Testers open the link in their phone browser, tap install, and they're running the build in seconds — the same OTA approach walked through in distributing iOS apps without TestFlight. Builds up to 512 MB are supported, and links are ephemeral, so stale betas clean themselves up instead of eating slots.

Summary

Hitting the 10,000 user limit is a "good problem" to have—it means your app is popular! Start by cleaning up inactive users, and if you truly need massive scale, consider if you are actually ready for the App Store production release instead of a beta.

Frequently Asked Questions

What is the limit for TestFlight external testers?

TestFlight allows up to 10,000 external testers per app. External testers are invited by email or through a public link, and the first build of each new version must pass Apple's Beta App Review before they can install it.

How many internal TestFlight testers can I have?

You can have up to 100 internal testers, and each internal tester can install on up to 30 devices. Internal testers must be members of your App Store Connect team, and their builds are available immediately without Beta App Review.

Do external testers require Beta App Review?

Yes. The first build of each new version you send to external testers must pass Apple's Beta App Review, which can add a wait before testers get the build. Later builds of the same version usually go out without another full review.

Does deleting a tester free up a spot?

Yes. If you remove a tester from a group in App Store Connect, that spot becomes available for someone new immediately. Because the 10,000 cap counts active slots rather than lifetime invites, pruning inactive testers is the simplest way to make room.

Can I pay for more TestFlight slots?

No. Apple does not offer an option to purchase additional TestFlight tester slots. The 10,000 external tester cap is fixed, so scaling past it means pruning testers, switching distribution method, or moving to a public release.

How can I distribute an iOS beta without a tester cap?

Upload your signed .ipa to BetaDrop and you get an instant over-the-air install link and QR code with no tester limit, no tester accounts, and no Beta App Review. Testers open the link in their phone browser and install directly. Builds can be up to 512 MB; registered builds expire within about 30 days, and anonymous guest links expire after 24 hours.

Have you hit TestFlight's tester cap? How did you work around it — Ad Hoc, Enterprise, or moving off TestFlight entirely?

How to Share Android APK Files for Testing

Kaushal Rola — Mon, 03 Aug 2026 17:19:12 +0000

Originally published on the BetaDrop blog.

Android makes app testing relatively simple compared to iOS. You can share APK files directly without complex signing requirements or device registration. But choosing the right method matters for tester experience and distribution efficiency.

This guide covers every practical way to share Android APK files for testing—from quick file transfers to professional distribution platforms.

Understanding Android APK Distribution

Unlike iOS, Android allows installing apps from any source—a process called "sideloading." This flexibility means you have multiple options for sharing test builds.

The only requirement: testers must enable "Install from unknown sources" (or grant install permission to the specific app they're using to download).

APK vs AAB: Which to Share?

Before sharing, understand the difference:

APK (Android Package) — The traditional format. A single file that installs directly on any compatible device. Best for testing.
AAB (Android App Bundle) — Google's newer format optimized for Play Store. Cannot be directly installed; Play Store generates device-specific APKs. Not ideal for direct testing.

Recommendation: Always share APK files for testing. If you're building AABs for Play Store, generate APKs separately for test distribution.

Method 1: Direct File Transfer

The simplest approach—just send the APK file directly.

Via Email

Attach the APK to an email
Tester opens email on their Android device
Tap the attachment to download and install

Limitations: Email attachment size limits (usually 25MB), some email providers block APKs, gets messy with multiple builds.

Via Messaging Apps

Slack, Discord, WhatsApp, Telegram all support file sharing
Send the APK directly in the chat
Testers download and install

Limitations: File size limits vary, some apps compress or rename files, version tracking becomes difficult.

Method 2: Cloud Storage Links

Upload to Google Drive, Dropbox, or similar services and share the link.

Google Drive

Upload APK to Google Drive
Right-click → Share → Get link
Set permissions to "Anyone with the link"
Share the link with testers

Pros: No file size issues, easy to update (just replace the file), familiar to most users.

Cons: Multiple clicks to download, testers may need Google account, no install analytics.

Method 3: Distribution Platform (Recommended)

Using a dedicated distribution platform like BetaDrop provides the best tester experience.

How It Works

Upload your APK file
Get a shareable install link
Share link with testers
Testers tap → download → install

Advantages

Clean install experience — Dedicated install page, not a file manager
No account required — Testers just need the link
App metadata displayed — Icon, name, version shown automatically
Cross-platform — Same platform for iOS and Android
Version history — Track multiple builds easily

BetaDrop supports APK files up to 512MB and provides instant download links with no account required for testers.

Method 4: Play Store Internal Testing

Google Play Console offers testing tracks for distributing through the Play Store.

Internal Testing Track

Up to 100 internal testers
Instant availability (no review)
Testers must be added by email
Requires Play Console access

For a detailed comparison, read our guide on APK vs Play Store Internal Testing.

Preparing Testers for APK Installation

First-time testers may need help enabling sideloading. Here's what to tell them:

For Android 8.0+ (Most Devices)

When prompted to install, Android asks for permission
Tap "Settings" in the prompt
Enable "Allow from this source" for the browser/app
Go back and tap Install

For Older Android

Go to Settings → Security
Enable "Unknown sources"
Proceed with installation

Generating APK Files

From Android Studio

Build → Build Bundle(s) / APK(s) → Build APK(s)
Find the APK in app/build/outputs/apk/

Debug vs Release APK

Debug APK — Quick to build, larger size, has debugging enabled. Fine for early testing.
Release APK — Optimized, smaller, signed with your release key. Use for later-stage testing.

Best Practices for APK Testing

1. Use Clear Versioning

Include version number and build date in your communications. Testers should always know which version they're testing.

2. Increment Version Codes

Always increment versionCode in your build.gradle. Android uses this to determine if an app can update over an existing installation.

3. Include Build Type Indicators

Modify your app name or icon for debug builds (e.g., "MyApp [DEBUG]"). This prevents confusion between production and test versions.

4. Provide Installation Instructions

Not all testers are technical. Include a quick guide with your shared link, especially for first-time sideloading.

5. Track Distribution

Know who has which version. Platforms like BetaDrop show download counts. For manual distribution, maintain a simple spreadsheet.

Troubleshooting APK Installation

"App not installed" Error

Signature mismatch — Trying to update an app signed with a different key. Uninstall the old version first.
Insufficient storage — Device needs space for the app.
Corrupted file — Download again or try a different transfer method.

"Parse error" or "Package is invalid"

APK was corrupted during transfer
APK targets a higher Android version than the device supports
APK architecture doesn't match device (ARM vs x86)

Installation Blocked

Unknown sources not enabled for this app
Corporate device policy blocking sideloading
Play Protect flagging unknown app (can be bypassed)

Frequently Asked Questions

How do I share an APK file with testers?

The best methods are: 1) Use a distribution platform like BetaDrop for the cleanest experience, 2) Share via cloud storage like Google Drive, or 3) Send directly through messaging apps or email.

Do testers need to enable unknown sources?

Yes. Android requires permission to install apps from outside the Play Store. On modern Android, this is done per-app when first installing.

What is the difference between APK and AAB?

APK is directly installable and best for testing. AAB is Google's format for Play Store that gets split into device-specific APKs during distribution.

Is sideloading APKs safe?

Yes, when you trust the source. Installing your own test builds is completely safe. Android's warnings exist because it can't verify the source like it can with Play Store apps.

Can I share the same APK with unlimited testers?

Yes. Unlike iOS, Android has no device registration limits. Anyone with the APK file or download link can install it.

Summary

Sharing Android APK files for testing is straightforward:

For quick, one-off shares: Direct file transfer or cloud storage links
For professional testing: Use BetaDrop for clean install pages and download tracking
For Play Store prep: Use internal testing tracks (but with more overhead)

The simplest approach for most teams: upload your Android app on BetaDrop and share the instant download link with your testers.

What's your go-to for sending an APK to a non-technical tester — a raw file over chat, Firebase, or an install link? Where does it usually go wrong?

How to Install IPA Files Over the Air (OTA)

Kaushal Rola — Mon, 03 Aug 2026 17:11:15 +0000

Originally published on the BetaDrop blog.

Installing IPA files over the air eliminates the need for iTunes or a Mac. Your testers can install your iOS app by simply tapping a link on their device. This guide explains exactly how OTA installation works and how to set it up.

Whether you're doing this manually or using a platform like BetaDrop, understanding the underlying process helps troubleshoot issues and make informed decisions.

What is OTA Installation?

OTA (Over-The-Air) installation is Apple's method for installing apps wirelessly without connecting to a computer. It's the same technology used by enterprise companies to distribute internal apps and by developers for beta testing.

The technology relies on the itms-services protocol, which tells iOS to fetch an app's installation manifest and download the IPA file directly.

How OTA Installation Works

Here's the technical flow when a user installs an IPA over the air:

User taps install link — A special URL starting with itms-services://
iOS fetches manifest — The URL points to a manifest.plist file on your server
Manifest parsed — iOS reads the app metadata and IPA download location
IPA downloaded — iOS downloads the IPA from the URL specified in the manifest
Installation prompt — User confirms they want to install the app
App installed — The app appears on the home screen

Requirements for OTA Installation

1. Properly Signed IPA

Your IPA must be signed with an Ad Hoc or Enterprise distribution profile. Development profiles won't work.

Ad Hoc — Requires device UDIDs in the provisioning profile. Limited to 100 devices per device type per year.
Enterprise — No device restrictions but requires Apple Developer Enterprise Program ($299/year).

2. HTTPS Server

Both your manifest.plist and IPA must be served over HTTPS with a valid SSL certificate. iOS rejects HTTP connections for security. This is non-negotiable.

3. Correct MIME Types

Your server must serve files with correct content types:

.plist → application/xml or text/xml
.ipa → application/octet-stream

The Manifest.plist File

The manifest is an XML property list that tells iOS about your app. Here's a complete example:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>items</key>
  <array>
    <dict>
      <key>assets</key>
      <array>
        <!-- Required: The IPA file -->
        <dict>
          <key>kind</key>
          <string>software-package</string>
          <key>url</key>
          <string>https://example.com/builds/myapp.ipa</string>
        </dict>

        <!-- Optional: Display icon -->
        <dict>
          <key>kind</key>
          <string>display-image</string>
          <key>url</key>
          <string>https://example.com/icons/icon-57.png</string>
        </dict>

        <!-- Optional: Full-size icon -->
        <dict>
          <key>kind</key>
          <string>full-size-image</string>
          <key>url</key>
          <string>https://example.com/icons/icon-512.png</string>
        </dict>
      </array>

      <key>metadata</key>
      <dict>
        <key>bundle-identifier</key>
        <string>com.yourcompany.appname</string>
        <key>bundle-version</key>
        <string>1.0.0</string>
        <key>kind</key>
        <string>software</string>
        <key>title</key>
        <string>My App Name</string>
      </dict>
    </dict>
  </array>
</dict>
</plist>

Required Manifest Fields

software-package URL — Direct HTTPS link to your IPA file
bundle-identifier — Must match your app's bundle ID exactly
bundle-version — Must match the version in your IPA
kind — Always "software" for apps
title — Display name shown during installation

Optional Icon Fields

Including display-image (57x57) and full-size-image (512x512) shows your app icon in the installation prompt. Without these, users see a generic placeholder.

Creating the Install Link

The install link follows this format:

itms-services://?action=download-manifest&url=https://example.com/manifest.plist

Key points:

The manifest URL must be HTTPS
The URL should be properly URL-encoded if it contains special characters
This link only works on iOS devices (Safari or compatible browsers)

Step-by-Step Manual Setup

Step 1: Export Your IPA

In Xcode, archive your app and export with Ad Hoc or Enterprise distribution. Make sure to select "Export for OTA installation" if prompted.

Step 2: Prepare Your Server

Upload to any HTTPS-enabled server. Verify MIME types are configured correctly. Test that files are directly accessible.

Step 3: Create the Manifest

Use the template above. Replace all URLs with your actual file locations. Match bundle-identifier exactly.

Step 4: Upload Files

Upload both the manifest.plist and IPA file. Note the exact manifest URL.

Step 5: Create Install Link

Construct the itms-services link using your manifest URL. Share this link with testers.

Automating OTA Setup

Manual setup is error-prone and tedious for every build. BetaDrop handles all of this automatically:

Upload your IPA file
We generate the manifest.plist automatically
Everything is hosted on HTTPS
Get your install link instantly

No server configuration. No XML editing. No SSL certificates to manage.

Troubleshooting OTA Installation

"Unable to Download App"

Common causes:

IPA not signed with Ad Hoc/Enterprise profile
Device UDID not in provisioning profile (Ad Hoc)
SSL certificate issues on your server
Incorrect MIME types
Bundle identifier mismatch between manifest and IPA

"Cannot Connect to Server"

Manifest or IPA URL is not accessible
Server is blocking iOS user agent
HTTP instead of HTTPS

"Untrusted Developer"

For Enterprise and some Ad Hoc apps, users must trust the certificate: Settings → General → VPN & Device Management → [Your Certificate] → Trust.

Link Opens Browser Instead of Installing

Some apps use embedded browsers that don't support itms-services. Tell testers to open the link in Safari.

Frequently Asked Questions

What is OTA installation for iOS?

OTA (Over-The-Air) installation lets iOS devices install apps directly from a web link without connecting to a computer. It uses Apple's itms-services protocol.

What is a manifest.plist file?

It's an XML configuration file that tells iOS where to download your app and provides metadata like bundle ID, version, and title.

Why does OTA installation require HTTPS?

Apple enforces HTTPS for security. iOS will not download apps from insecure HTTP connections.

Can I install any IPA over the air?

No. Only IPAs signed with Ad Hoc (with registered device UDIDs) or Enterprise distribution profiles work for OTA installation.

How long do OTA install links last?

As long as your files remain on the server and the signing certificate is valid. With BetaDrop, your build and install link stay live for 30 days (24 hours for anonymous guest links) — with no servers or certificates for you to manage.

Summary

Installing IPA files over the air requires:

A properly signed IPA (Ad Hoc or Enterprise)
HTTPS hosting with valid SSL
A correctly formatted manifest.plist
An itms-services:// install link

While you can set this up manually, BetaDrop automates the entire process. Upload your IPA and get an install link in seconds—no server setup required.

Need faster distribution? Upload your iOS IPA on BetaDrop and start sharing with testers immediately.

How are you getting builds onto testers' iPhones today — TestFlight, Diawi, or self-hosted OTA? What trips you up most: code signing, MIME types, or the Untrusted Developer prompt? Let me know in the comments.