Launch Xcode and select Build -> Build and Archive. The organizer will pop out. Select the assembly you want to publish and click the Share button above the list. Then select the identifier with which you want to sign your code (usually this is the same as that you use to sign the code for standard deployment on the device). Click, then, on Distribuite for Enterprise ..
At this point, a form will appear in which you ask from which URL the application should be downloaded. Suppose your site is available at www.example.com and your application (.ipa file) is located at www.example.com/download/myapp.ipa, then http://www.example.com/download/ myapp.ipa should go in this field. [Cm. Update below] Fill in other fields as you wish; you can get more information about this in the Apple documentation
As soon as you fill out the form and click OK, select the place where you want to save the generated files (ipa and plist).
Now complex things come up when you have to deal with server-side code. I created a small sample page below. Remember that you must overlay all the files on your website: myapp.ipa, myapp.plist and myapp.mobileprovision.
<!DOCTYPE HTML> <html> <head> <title>Install your application</title> </head> <body> <ul> <li> <a href="http://www.example.com/download/myapp.mobileprovision">Install Team Provisioning File</a></li> <li><a href="itms-services://?action=download-manifest&url=http%3A%2F%2Fwww.example.com%2Fdownload%2Fmyapp.plist">Install Application</a></li> </ul> </div> </body> </html>
Note that the second href is just a plain old fashioned URL. Nothing special about that. If you are curious about these strange% 2F and% 3A, they are ordinary characters with urlencoded (for "/ and": respectively). When you do this, you will definitely be done.
This answer was taken as part of a blog that I made in 2010. Here you can read the full version.
Fabiano Francesconi Dec 22 2018-10-22T00: 00Z
source share