You have archived your iOS app in Xcode, perhaps already uploaded that archive to App Store Connect, and now want to install its Release build on your own iPhone without waiting for TestFlight processing.
You can export the same archive with Xcode’s Release Testing distribution method, then install the resulting .ipa through Xcode.
There is one important distinction:
The exported app comes from the same archive, but Xcode re-signs it for installation on registered devices instead of App Store distribution.
Its executable, resources, and build number come from the archive. The code signature and provisioning profile are different so the app can run on your registered iPhone.
This is a device-registration workflow, not a replacement for TestFlight. It is useful for your own devices and other devices registered with your developer team. Use TestFlight when you need to distribute the build to testers who are not registered with your team.
What you need
Before starting, make sure:
- You have a valid iOS archive whose Archive action used the Release configuration you want to test.
- Your Apple Developer Program account and team are available in Xcode.
- Your iPhone is paired with your Mac, unlocked, and trusted.
- Your iPhone is registered with your developer team. With automatic signing, Xcode can register a connected device for you if your account has permission.
- Developer Mode is enabled on the iPhone if Xcode requests it. On the device, open Settings → Privacy & Security → Developer Mode, enable it, restart, and confirm the prompt.
Apple’s distribution guide explains the available archive distribution methods, and its registered-device guide documents installing an exported app with Xcode.
Step 1: Open the archive in Xcode Organizer
In Xcode, open:
Window → Organizer
Select Archives, then choose the archive you want to test. It can be the same archive you uploaded to App Store Connect; it does not need to be rebuilt.
Click Distribute App.
Why use the same archive?
Using the existing archive avoids creating a new build. The executable, bundled resources, compiler optimizations, and build configuration all come from the archived build.
That makes this result more representative of the build you uploaded than rebuilding the project and running it from Xcode again.
Step 2: Choose “Release Testing”
Xcode shows several distribution methods. Choose:
Release Testing
Then continue through the prompts.
Why choose Release Testing?
Release Testing is Xcode’s preconfigured workflow for exporting a release build to devices registered with your team. It uses automatic code signing similar to the App Store option, but produces an export you can install on registered devices.
The other common choices serve different purposes:
- TestFlight & App Store uploads the build to Apple for TestFlight or App Store distribution.
- TestFlight Internal Only, when available, still depends on App Store Connect processing.
- Debugging uses development signing and is intended for debugging.
- Enterprise is for organizations enrolled in the Apple Developer Enterprise Program.
The exact options vary by Xcode version, platform, and team, but Release Testing is the setting to look for in the standard iOS flow.
Step 3: Choose the export options
Some Xcode versions show export options after you select Release Testing. If you see App Thinning, choose:
App Thinning: None
Why choose None?
App thinning creates device-specific variants of an app. None exports one unthinned IPA, which is the simplest option when you are installing the build on one connected iPhone.
If you are testing several device variants or measuring download and installation sizes, choose All compatible device variants instead. Xcode can then export a universal IPA along with thinned variants and a size report.
For this single-device workflow, the unthinned export keeps the process easy to inspect and install.
Step 4: Keep the normal release options
If Xcode shows Strip Swift symbols, leave its default setting enabled.
This keeps the exported package aligned with normal release packaging and can reduce the size of the distributed binaries. It does not remove the archive’s dSYM files; keep the original archive if you need to symbolicate crash reports later.
If Xcode shows Include manifest for over-the-air installation, leave it unchecked unless you intend to host the IPA yourself.
An over-the-air manifest is for hosting the IPA and manifest on an HTTPS server so users can install the app from a link. That requires additional infrastructure and is unnecessary when the iPhone is connected to your Mac.
Click Next or continue to the signing step, depending on the Xcode version.
Step 5: Use automatic signing
On the signing screen, choose:
Automatically manage signing
Select the same Apple Developer team used by the app.
Why use automatic signing?
The exported IPA needs a provisioning profile that authorizes the registered iPhone. Automatic signing lets Xcode manage the signing certificate, provisioning profile, device registration, bundle identifier, and supported entitlements.
If the iPhone is not registered, connect and unlock it, select it as a run destination, and allow Xcode to register it with your team. If the app uses extensions or capabilities that require special provisioning, every target needs a compatible signing configuration.
Step 6: Review the signing details
Before exporting, Xcode shows a summary of the selected team, signing assets, and entitlements.
Confirm that:
- The correct development team is selected.
- The distribution method is Release Testing or the registered-device equivalent.
- The expected bundle identifier is shown.
- The provisioning profile includes the iPhone.
- There are no entitlement or provisioning errors.
The most common direct-installation failures are signing mismatches, such as a missing device, the wrong team, an extension with an incompatible profile, or an entitlement that the selected profile does not allow.
Step 7: Export the IPA
Continue through the workflow and click Export. Choose a folder on your Mac.
Xcode exports a folder containing the .ipa file and may also include export logs or other distribution files.
An IPA is the installable package for an iOS app outside the normal App Store installation flow. In this case, it contains the app from your archive with signing that authorizes installation on registered devices.
Step 8: Open Devices and Simulators
Connect and unlock your iPhone, then open:
Window → Devices and Simulators
Select your iPhone in the sidebar.
Why install through Xcode?
Xcode communicates directly with the connected device, so you do not need to host the IPA or create an over-the-air manifest. It also reports signing and provisioning errors during installation.
Step 9: Install the exported IPA
In the device details window, find Installed Apps.
Then either:
- Click the
+button and choose the exported.ipafile. - Drag the
.ipadirectly into the Installed Apps area.
Xcode copies the application to the iPhone and installs it. When installation finishes, the app should appear on the Home Screen or in the App Library.
Step 10: Launch the app on the iPhone
Open the app normally from the iPhone.
Because the app was exported through Release Testing, it runs as a release-distributed app rather than as a build launched with the Xcode debugger attached. On iOS, IPA-based apps require Developer Mode to run.
This makes the workflow useful for testing:
- Compiler optimization issues
- Differences between Debug and Release configurations
- Production API settings and release feature flags
- App startup outside the Xcode debugger
- Push notification and entitlement behavior
- Performance characteristics of an optimized build
Is it exactly the same as the TestFlight build?
It is the same archived application build, but it is not the same signed package or delivery pipeline.
The App Store Connect upload is prepared for Apple’s distribution process and cannot be installed manually on an iPhone. The Release Testing export is signed for registered-device installation.
| Component | App Store Connect upload | Release Testing export |
|---|---|---|
| Source archive | Same | Same |
| Archived executable and resources | Same archived build | Same archived build |
| Build number | Same | Same |
| Provisioning profile permits direct installation | No | Yes |
| Apple processing required before testers can install it | Yes | No |
| Direct installation | No | Yes |
| Registered device required | No | Yes |
Apple can apply additional processing to builds distributed through the App Store or TestFlight. Direct installation is therefore a useful test of the archived Release build, but it does not reproduce every part of Apple’s final store-delivery pipeline.
Common problems
“The application could not be installed”
The most likely cause is that the iPhone is not included in the provisioning profile, or the profile no longer matches the signed app.
Connect the device to Xcode, confirm that it belongs to the correct team, and export the IPA again using automatic signing. Also confirm that the device has enough free storage and that the app’s minimum iOS version is supported by the phone.
The app installs but will not launch
Confirm that Developer Mode is enabled. If it is already enabled, check the device logs in Xcode for:
- Missing entitlements
- An incorrect production configuration
- A code-signing problem in an embedded framework
- An extension signed with the wrong profile
- A Release-only runtime crash
Xcode does not show the iPhone
Make sure:
- The iPhone is unlocked.
- You selected Trust This Computer.
- Developer Mode is enabled if Xcode requests it.
- The cable supports data, not only charging.
- The Mac and iPhone run compatible software versions.
Apple’s Developer Mode documentation explains when the setting appears and how to enable it.
Release Testing is unavailable
Confirm that:
- You are enrolled in the paid Apple Developer Program.
- Xcode can access the correct developer team.
- The archive is a valid iOS application archive.
- The app and its extensions have valid signing capabilities.
Final workflow
The full process is:
Xcode Organizer → Archives → select the archive → Distribute App → Release Testing → optional export settings → automatic signing → Export IPA → Devices and Simulators → install IPA
If your Xcode version does not display the optional export settings, continue with automatic signing and export the IPA.
This is a quick way to put an archived Release build on your own registered iPhone without waiting for TestFlight processing.