CODEWITHSUNDEEP
iosotaenterprise-distribution
Mark Jackson
Mark Jackson

Reputation: 91

Concise guide to OTA distribution of iOS Apps

Is there a concise guide to signing and distributing apps over the air for iOS? We have an extremely simple app to be distributed in-house to five or six users. Not going to get a $10000 MDM solution.

Apple's documentation is absolutely incomprehensible.

Sorry, been futzing with this for two days.

We have an iOS app. I can install it on my phone for debugging using xcode. Runs perfectly.

We loaded the plist, ipa, and icons onto an IIS server. The IIS Server is secured using an SSL cert. You have to log in, and then click on a link to be taken to the page with the download link. So even getting to the link means you have authenticated.

All the links in the plist file are https links.

I can manually type the https address for the plist file and I get an XML file in Chrome or Safari from my PC, my Mac, or my iPhone.

If a person hits the link on an iPhone, "cannot connect to server www.example.com". In the iPhone console, I see the error message SSErrorDomain Code=2 cannot log into iTunes.

Driving me crazy. As best as I can tell, the itms prefix is not using the https link, but how to tell?

Upvotes: 3

Views: 1062

Answers (2)

Mark Jackson
Mark Jackson

Reputation: 91

Got it to work. Praise the Lord.

I moved the ~/app directory from a server that required authentication to one that does not but only holds the app and nothing else. The server is secured by a SSL certificate issued by GoDaddy so it's not self signed.

I think that Apple was trying to come back to the site somehow to check something and the authentication/redirection was blowing that up.

I also edited the plist and index.html files manually removing all white space (tabs & spaces) which had been inserted.

Gonna test it on a wider audience now.

Upvotes: 0

Matteo Pacini
Matteo Pacini

Reputation: 22846

For in-house distribution (outside the App Store), you need to have an enterprise developer account, and sign the app with an Ad Hoc Provisioning profile.

If you don't have an enterprise account, you'll have to specify a list of devices when creating the provisioning profile (not recommended).

You could then host the app on a web server, and have the users download it through Safari.

Upvotes: 0

Related Questions