Ad-Hoc Distribution for Xamarin.iOS Apps
This document gives an overview of the Ad Hoc distribution techniques that are primarily used for testing an Xamarin.iOS applications with a wide group of people.
Once an Xamarin.iOS app has been developed, the next step in the software development lifecycle is to distribute the app to users for testing.
iTunes Connect is one option for managing app testing and is described more in the TestFlight guide. However, members of the Apple Developer Enterprise Program do not have access to iTunes connect, so Ad Hoc distribution is the best method of testing these apps.
Xamarin.iOS applications can be user-tested via ad hoc distribution, which is available on both the Apple Developer Program and the Apple Developer Enterprise Program, and allows up to 100 iOS devices to be tested.
Ad hoc distribution has the advantage of not requiring App Store approval, and it can be installed over-the-air from a web server, or via iTunes. It is, however, limited to 100 devices per membership year, for both development and distribution, and these must be manually added in the Member Center by their UDID. For more information on adding devices, visit the Device Provisioning guide.
Ad hoc distribution requires that applications be provisioned using an Ad Hoc provisioning profile containing code signing information, as well as the identity of the application and the devices that can install the application.
This guide will provide information on Provisioning for Ad Hoc distribution, and information on how to distribute a Xamarin.iOS app.
Setting Up for Distribution
Even if you plan to release a Xamarin.iOS application for In-House Deployment, for testing purposes, you'll need to build an Ad Hoc Distribution Provisioning Profile specific to it. This profile allows an application to be digitally signed for release so that it can be installed on an iOS device.
The next section will describe how to get set up with a Distribution Certificate and a Distribution Provisioning Profile.
Only Team Agents and Admins can create Distribution Certificates and Provisioning Profiles.
Create a Distribution Certificate
Browse to the Certificates, Identifiers & Profiles section of the Apple Developer Member Center.
Under Certificates, select Production.
Click the + button to create a new Certificate.
Under the Production heading, select In-House and Ad Hoc, or App Store and Ad Hoc, depending on your program membership:
Click Continue, and follow the instructions to create a Certificate Signing Request via Keychain Access:
Once you have created the CSR as instructed, click Continue, and upload the CSR to the Member Center:
Click Generate to create a certificate.
Finally, Download the completed certificate and double-click on the file to install it.
At this point, the certificate should be installed on the machine, but you may need to Refresh your profiles to ensure that they are visible in Xcode.
Alternatively, it is possible to request a Certificate via the Preferences dialog in Xcode. To do this, follow the steps below:
Create a Distribution Provisioning Profile
Create an App ID
As with any other Provisioning Profile you create, an App ID will be required to identify the App that will be distributed to the user's device. If you haven't already created this, follow the steps below to create one:
- In the Apple Developer Center browse to the Certificate, Identifiers and Profiles section. Select App IDs under Identifiers.
- Click the + button and provide a Name which will identify it in the Portal.
- The App prefix should be already set as your Team ID, and cannot be changed. Select either an Explicit or Wildcard App ID, and enter a Bundle ID in a reverse DNS format like:
- Select any App Services that your app requires.
- Click the Continue button and follow the on screen instructions to create the new App ID.
Once you have the required components needed for creating a Distribution Profile, follow the steps below to create it:
Click the + button and select the type of Distribution Profile that you want to create as Ad-Hoc:
Click the Continue button and select App ID from the dropdown list that you want to create a Distribution Profile for:
Click the Continue button and select distribution certificate required to sign the application:
Click the Continue button and enter a Name for the new Distribution Profile:
Click the Generate button to create the new profile and finalize the process.
You may have to quit Visual Studio for Mac and have Xcode refresh its list of available Signing Identities and Provisioning Profiles (by following the instructions in the Downloading Profiles and Certificates in Xcode section) before a new Distribution Profile is available in Visual Studio for Mac.
Selecting a Distribution Profile in a Xamarin.iOS Project
When you are ready to do a final build of a Xamarin.iOS application, select the Distribution Profile that was created above.
In Visual Studio for Mac, do the following:
Double-click the project name in the Solution Explorer to open it for edit.
Select iOS Bundle Signing and the type of build from the Configuration dropdown:
In most cases, the Signing Identity and the Provisioning Profile can be left as a default values of Automatic and Visual Studio for Mac will choose the correct profile, based on the Bundle Identifier in the Info.plist:
If required, select the Signing Identity and Distribution Profile (the one created above) from the drop-downs:
Click the OK button to save the changes.
Ad Hoc Distribution
While TestFlight is a popular means of beta testing and distribution, it is part of iTunes Connect, and is therefore unavailable to members of the Apple Developer Enterprise Program.
Ad Hoc Distribution allows developers to beta test apps on a wide range of devices when iTunes connect is not an option. Ad-Hoc works in a similar way to In-House Distribution, and requires an IPA to be created, which can then be distributed either over-the-air, or manually via iTunes.
IPA Support for Ad Hoc Deployment
Once provisioned, applications can be packaged into a file known as an IPA. This is a zip file that contains the application, along with additional metadata and icons. The IPA is used to add an application locally into iTunes so that it can be synced directly to a device that is included in the provisioning profile.
For more information on creating an IPA, see IPA Support guide.
This article explained the Ad Hoc distribution mechanisms, which are required for testing Xamarin.iOS applications.