- Home
- Deploying
- iOS deployment
- Deploying an iOS app for external testing
Deploying an iOS app for external testing
Before deploying your app to the App Store, you might want to release it to external testers who can test it on their devices outside the development environment. If you do not want to use Testflight, then you can do this by exporting an IPA file with the app-store export method.
Before deploying your app to the App Store, you might want to release it to external testers
who can test it on their devices outside the development environment. If you do not want to use Testflight, then you can do this by exporting an IPA file with the ad-hoc export method.
Using Testflight
If you wish to invite external testers using Testflight, you CANNOT use the ad-hoc export method. You need an IPA with the app-store export method.
-
Generate an IPA file on your own machine at least once.
-
Upload all necessary code signing files to Bitrise.
For the
ad-hocexport method, you need a Distribution type certificate and an Ad Hoc type provisioning profile. Only upload a provisioning profile if you use manual provisioning: iOS code signing with manual provisioning. -
Make sure the Xcode Archive & Export for iOS Step is in your Workflow.
-
Set the Distribution method input of the Step to
ad-hoc. -
Set the Automatic code signing method input to the Apple service connection you want to use for code signing. The available options are:
-
offif you don’t do automatic code signing. -
api-keyif you use API key authorization. -
apple-idif you use Apple ID authorization.
-
-
Make sure you have the Deploy to Bitrise.io Step in your Workflow.
-
Start a build.
-
When the build is finished, go to the app’s Builds page and click the latest build.
-
Click the Artifacts tab to find your IPA file that you can distribute.
An app on Bitrise represents a Git repository that stores source code and has been connected to Bitrise to be able to run builds on it. As such, a Bitrise app isn't necessarily an actual application: it's just the code on which you run builds with Bitrise.
A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.
A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.