Having some issues with this. Testing on my device, which is UUID approved. Error I get when accessing OTA url on device is: There was a problem processing your request. This applications download directory could not be found? I've read a few threads here on this already, but they dont seem to apply. For instance, this tutorial: https://dl.dropboxusercontent.com/u/115208762/iOS_OTA.pdf I dont have the Distribute button in xCode (maybe newer versions dont have this anymore)? My certs should be squared away as I have successfully pushed the app to other devices using our MDM provider (Meraki). However, for testing, using MDM is a bit overkill and a pain for testers to first setup.. thus, I'm trying to get BT OTA to work, instead. One issue of not having the Distribute button, I think, is that a plist file is not generated for me. I have tried copying out the BT_info.plist file, renaming to app.plist, and adding the URL/String to it, like so: <key>URL</url> <string>http://mydomain.com/BT-server/files/applications/EAB864B133B4D8D4713E86A32/install-ios/app.ipa</string> I upload the app and plist to OTA admin console, and I see it in the corresponding directory above.. all this produces the same error as previously mentioned. I suspect either im missing something else in my plist file, or its another Red Hat permissions issue. Note: providing a direct download to the .ipa itself does not work either (browser cannot open file). Has anyone tried OTA using the newest Xcode (6.1.1)? This is for Enterprise/Ad-Hoc distribution. Can someone post an example of their working .plist file to see if im missing anything? If permissions related, where/what should I change? Thanks!

Did you get your self hosted issue resolved? This doesn't sound like an OTA issue. That will begin when the app downloads halfway and stops. This sounds like you've still got issues with your self hosted installation. Cheers! -- Smug

I did.. thus having an app to distribute OTA... :)

But the error you're getting doesn't reflect OTA... it reflects self hosting issues... OTA works just fine; Rawls Enterprises did some work on it, and I documented their work in a little How to document. Which, by the way, the document you're using is outdated; use this one: https://www.buzztouch.com/files/howtos/BTOTA.pdf The problem you'll get with OTA is typically 'code-signing' issues, with respect to your provisioning cert and the devices used. Try making the changes required in this OTA document, and see if it helps. Cheers! -- Smug

Note: Runnin' so quick... I know for a FACT that OTA on iOS will NO LONGER WORK on an unsecure URL. In other words, your app's download URL cannot begin with... http://mydomain.com/... it must begin with... https://mydomain.com/.... This is a recent change and for sure a gotcha. There are some other differences in the way Xcode's dialogue boxes look / work now, compared to before, but it looks like you have that figured out?

Interesting. Thanks for that tidbit, David! Cheers! -- Smug