How to Install IPA on iPhone and Share Builds With Your Team
AppShare gives mobile app developer teams a complete build distribution workflow for iPhone and Android: create an app, upload a release, decide who's allowed to access it, and track every install and piece of feedback that comes back, without losing version history, tester context, or access control along the way.
Before You Start
Everything You'll Manage Along the Way
Before your first upload, it helps to know what each part of AppShare is actually for. These are the four things most teams touch on every release.
Quick Releases
Not every build needs a full app entry first. Quick Release lets you upload a one-off
.apkor.ipa, add an optional expiry or password, and get an install link back immediately, no extra setup.UDID Manager
A UDID is the unique identifier for one iOS device. An ad hoc build installs only on devices whose UDIDs are in its provisioning profile, so testers add their device’s UDID and model here, and developers include those devices when signing the next build.
Tester Management
Every app keeps its own tester list, built by inviting people individually or in groups. Lists stay separate per app, so a client's testers and an internal QA group never end up mixed together.
Password Protection
A release's install page can stay fully public, or sit behind a password you set in release settings, useful for a pre-release build or a client demo you'd rather keep contained for now.
WHOLE CYCLE
How to Distribute Mobile Apps in Six Steps
Here’s how to distribute mobile apps with AppShare, from first upload to every update.
STEP 1
Create an Application
Every release starts with an app record. Set it up once, and every future build, tester list, and public page for this app builds on top of it, without getting mixed up with your other projects.
- 1
App Name
Up to 24 characters, shown right on the public install page, so testers know what they're looking at.
- 2
Shareable Link
Choose a Unique URL, generated fresh each release, or a Persistent URL that stays the same over time.
- 3
App Stage & Alerts
Set the app's current stage and configure alert settings before the very first build even lands.
- 1
Dashboard Upload
Drag in an .apk or .ipa, up to 2GB, straight from your desktop, no other steps needed.
- 2
CLI Upload
Push a build from your terminal using your app's App ID, no dashboard trip required at all.
- 3
CI/CD Upload
Trigger an upload automatically from GitHub Actions, GitLab CI/CD, Bitrise, Jenkins, or others.
STEP 2
Upload Your Build
A build reaches AppShare from wherever your team already works: the dashboard, a terminal, or a pipeline. Every upload path ends up in the same place, one release, ready to configure.
Step 3
Configure Release Settings
Before anyone gets a link, decide what they're allowed to do with it. Release settings covers who can access the build, how long it stays live, and what context they see before installing.
- 1
Public or Private
Keep the release open to anyone with the link, or lock it behind a password.
- 2
Expiry Date
Set how long the release stays installable, so an old build doesn't quietly stay live.
- 3
Release Notes
Add a short note on what changed, and a Change Log entry for anything with more detail.
- 1
Page Link
A public page with build details, ready to open in any browser, no app needed.
- 2
Install Link
A direct link that triggers the install itself, one tap and it's underway.
- 3
QR Code
Scan-to-install, for anyone testing from a physical device in the room.
- 4
Page Customization
Add your logo, favicon, color theme, or a custom domain, your call on layout.
Step 4
Install Page Is Created
The moment release settings are saved, AppShare generates a dedicated install page for that build, ready to share however works best for whoever's on the other end.
Step 5
Others Install and Give Feedback
From here, it's out of your hands until someone installs it. Testers open the page, install the build, and can post directly into that release's forum if something needs flagging.
- 1
No Store Account Needed
Testers install straight from the link, no App Store or Play Store account needed at all.
- 2
Device Registration (iOS)
For an ad hoc build, only devices whose UDID was added and encoded into that build can install.
- 3
Release Forum
Testers and your team post comments and attachments directly on that release, tied to the exact build.
- 1
Unique URL
Every release gets its own link automatically, generated fresh and never reused for the next one.
- 2
Persistent URL
One custom-slug link covers the app's entire release history, so testers only need one bookmark.
- 3
Show Old Releases
Toggle older releases visible or hidden on the public page, so testers can reach a past version.
Step 6
Push New Builds
A release rarely stays static. When it's time for the next version, you decide whether testers land on a brand new link each time, or the same one, updated in place.
On the iPhone
How to Install an IPA on iPhone
Once the build is uploaded, testers install it straight from the link. No App Store, no TestFlight.
Notifications
Get Notified as the Workflow Moves
A release doesn’t stop mattering once the link goes out. AppShare notifies your team the moment a new build goes live through Slack, Microsoft Teams, Discord, Telegram, Email, SMS, voice call, push notifications, Zapier, or Webhooks, so nobody has to check the dashboard to know it’s ready.
FAQ
Questions About the Release Workflow
Do I need to set up an app before sharing a build?
No. Quick Release lets you upload a single .apk or .ipa without creating a full app first. Add an optional expiry or password, and AppShare returns an install link and QR code immediately. Set up a full app when you need version history, a dedicated tester list, and a release forum.
How to install IPA on iPhone without the App Store?
Open the AppShare install link or scan the QR code on your iPhone, tap Install, and the app appears on your home screen. Ad hoc builds only install on devices whose UDID is included in the build. In-house builds also need the developer trusted under Settings > General > VPN & Device Management first.
How do I share an app build with my team
Upload the .ipa or .apk, set it public or password-protected, and AppShare generates an install link, a QR code, and a public page. Send whichever fits, and teammates install straight from it. Each app keeps its own tester list, so internal QA and client testers never end up mixed together.
What's the difference between a Unique URL and a Persistent URL?
A Unique URL is generated automatically for each release and cannot be customized, so every build gets its own link. A Persistent URL uses a custom slug and stays the same across releases, so testers keep one bookmark and always reach the latest build. You can also show or hide older releases there.
Can I keep a build private?
Yes. Set the release to private in release settings and add a password, so only people who have it can open the install page. You can also set an expiry date so the build stops being installable after a set time, which suits pre-release builds and client demos you want kept contained.
Why won’t an IPA install on my iPhone
Usually because the iPhone is not registered for that build. An ad hoc IPA only installs on devices whose UDID was added before the build was signed. Add the device and its model in the AppShare UDID Manager, include it in a new build, then upload it and share the fresh install link.
Start Now
From Upload to Install, Start to Finish
That’s how to share an app build with your team: create your first app, upload a build, and hand over an install link.