I'm curious if anyone else has this issue. I searched, but saw nothing specific. Summary: Android Install OTA no problem. iOS Install OTA dies 3/4 way in... So... I've created a BT App. I'm self hosting now, so it's on BT Server v2.1.7 - So far, things are running smoothly, just like the BT site. I'm impressed. But I digress... I've created this app. I've bled to Apple and am a Certifiable Developer. I have all the correct certs and keys and stuff. I've created all the right keys in Eclipse. I've created the app. I've compiled the app. I've signed the app. It all flows smooth, both Android via Eclipse, and iOS via Xcode. I test the App in the Android Simulator; works fine. Great. I test the App on my Samsung Galaxy Tab II; works fine. Great. I test the App in the Xcode Simulators; works fine. Great. I test the App on my iPhone 3GS iOS 6.0.1; works fine. Great. I test the App on my 1st Gen iPad iOS 5.1.1; works fine. Great. I compile the App, and toss the apk in the Android; works fine. Great. I compile the App, and toss the ipa into iTunes, and Sync my 3GS and 1G iPad; works fine. Great. I upload the app.apk via the OTA control panel of the server. I upload the app.plist and app.ipa via the OTA control panel of the server. I download and install the Android apk on my Galaxy. works fine. Great. I download off my iPhone and about 3/4 of the way, it dies. I have to delete a poor looking icon with a progress bar stuck around 75%. I download off my iPad and about 3/4 of the way, it dies. I have to delete a poor looking icon with a progress bar stuck around 75%. Sorry for the long windedness; sometimes talking it through my head as I type helps. Not this time, I guess. I 'suspect' it's those darn apple provisioning profiles, but it 'works' tethered, and it 'works' via iTunes (drop the app on iTunes; sync the device; run the app). Both of those activities didn't happen before I got my developer certs. And it took a while to get the certs correctly installed and in place. I've done it a few times now, and I think I have it down, lol! The Android side works perfect, so I'm pretty confident the delivery system. I've tested with 2 different test apps, and two different iOS devices on different iOS versions. same results on all of them. For the interim, it's not a 'killer'; I can just send someone a link off my server and they can download it. Heck, even the URL will be easier to digest. But I'd like it to work eventually. Any ideas or 'provisioning profile' remedies? Cheers! -- Smug

This is puzzling. I'm fairly certain it's some kind of provisioning deal, or just some kind of Apple deal... I created a new App ID, a new Provision, and a new App. All devices provisioned in the profiles. They have 'green' lights in the organizer when connected to the computer. Same results. Things that make me go hmmm....

Hmm...yes, this does seem strange. I've not experienced it before but it should be easy enough to debug...right? Maybe have a look at the HTML for the install page using a regular browser. Make sure the markup looks right, no typos, etc. If you have not done this before it's pretty easy to figure out. You could Google for some tutorials too (in terms of what the HTML should look like). The Self Hosted control panel doesn't do much in this regard other than help you stay organized. In other words, you could easily transfer the files to a folder on your site using FTP to test that way. It's a matter of getting the app, and the necessary files in the same directory along with the proper markup in the HTML. Not sure what else to add here but can say that I have use the same process you described lots and lots of times. I'll bet it's something screwy with the Provisioning Profile + Build Settings. Wish I could lend more help.

If you are seeing an icon and it is trying to download you must be making a connection. I have had large Ad Hoc builds do this on download if the connection gets interrupted (or is very slow) during the download. I was using Testflight when this happened. I would think it has to do with this rather then an Apple issue. Now if when you try to open it, it flashes then goes to the home screen I would look to a profile issue.

Hey Smug, If you need another tester, I can test it on my IPhone. That's not helping with the Apple issue but just saying. LA

Hello SmugWimp, Read this great article, it documents the necessary steps for enabling Over-The-Air Wireless Distribution of iOS apps. Amazingly enough, this company primarily does Microsoft-based solutions for their clients, yet they still did a terrific documentation job! http://blog.appliedis.com/2012/10/29/wireless-distribution-of-enterprise-ios-apps/ You need two basic things: 1. An Enterprise account with Apple. It is $299 instead of $99, which means you will be paying Apple twice. An Enterprise Dev Account allows for physical and wireless distribution of apps within a Company, but no apps are allowed for distribution via Apple's App Store. 2. Be in charge of your Apache or IIS Web Server such that you can modify its configuration. I had successfully done this back in late 2010 within a Company, but had to stop the OTA Installs for non-technical reasons. It does work -- at a greater expense and at a higher logistics cost of switching accounts. Tethering to iTunes, wirelessly connecting to TestFlight or implementing your Enterprise account with the open-source Hockey app are other choices. Best luck! -- Niraj

Thanks for the suggestions, folks! Niraj, I found that site last night, but waited until this morning to read into it; Fortunately you can do all the stuff without the enterprise account, as long as you have access to your servers. I setup a quickie test 'distribution' page, but really it's the same as the BT OTA page with less frills. And the same results. Regardless of the app. regardless of the device, regardless of the AppID, it downloads about 75% and kerplooey. No problems at all with it tethered locally, either from Xcode, or from iTunes. Only 'over the air' and only products for Apple. Android works fine. I'm convinced it's an Apple thing... if nothing else it's certainly 'related' to Apple. All crazy things in my life are somehow related to Apple... As David mentioned, quite possibly a build thing. Someone pass me a shovel, I'll be digging for a while... Cheers! -- Smug

Wow! How weird is this? Ok, you know I can't download/install over the air using the BT method, and I was thinking it was provisioning. It's not. It's the plist, and the URL. When I 'archive' my app, and then select to distribute it (Enterprise), I enter in the URL provided to me by the BuzzTouch control panel for that app, in the 'OTA' page. It ends up looking like, "http://myserver.com/?id=G0BBLYG00KL3TT3RSNuMB3RS" Well, apparently my server is too snobby for dynamic references. I tried the same files in a test directory, and it failed. When I edited the plist URL to reflect the test directory (http://myserver.com/test/app.ipa) it worked! (and it explains why it didn't work in previous attempts; incorrect url in the plist) I then tried the 'SAME PHYSICAL FILE' again in BT (plist updated to attempt both with and without the "&platform=iOS" appended to the gobbledygook letters, but still no go. I corrected the physical path to the BT directory in my plist to reflect the 'actual' directory that the ipa resided in: http://myserver.com/files/applications/gobbledygook/install-ios/app.ipa and it works! For the moment, I'll just need to remember to assemble the correct 'literal' URL during the creation process. It's not how the server delivers the app, so much as how the app interprets the URL from the plist. No wonder I have no issues with Android; they don't care. Now, am "I" the only one with this issue? Could it be a mime thing? I have hosted servers through Network Solutions, but I'm not certain if I can alter my apache setup with respect to mime types... Let me know your thoughts and ideas... Cheers! -- Smug

Glad you got it sorted out! Good to know that an Enterprise account is not necessary. And that you can archive it with Enterprise distribution settings. If it works with the physical path, then the Apache settings must already have the configuration (and MIME type) required by Apple?

Ya, probably not really Mime types, because it 'does' work... it just doesn't work with that odd URL. As long as I edit my 'app.plist' to reflect the actual 'path', we're good. Just one more step that needs to be done, and not a difficult one. Thanks for checking in! Cheers! -- Smug