I'm developing an iOS app for iPhone and iPad. It runs great on the simulators and actual devices. It installs without error using both iTunes and the iPhone Configuration Utility. I cannot, however, seem to get wireless distribution to work properly.
Sanity checks:
Just to be clear, this installs PERFECTLY via iTunes and the iPhone Configuration Utility. I have read countless blogs and articles on how to get this working, but no one seems to have definitive answers. Is there ANYONE that can think of what is going wrong here??? Thanks in advance. Pulling my hair out.
Apple offer two solutions for this: Apple Developer Enterprise Program, This allows you to distribute your app as a URL via your internal site or web server. Volume Purchase Program for enterprises, This allows you to distribute apps via a URL to managed devices within your organisation.
You can share the html link to your users and they would be able to download the app by clicking “Install iOS in-house App” on your html. After downloading the app, users needs to Trust the certificate under Settings → General → Device Management → <Enterprise Name> then only they would be able to open the app.
NovaJoe -- I was pretty discouraged to review your link as it does appear to read that you need Enterprise Developer license...
I think I figured it out. Read the first paragraph and first bullet point: http://developer.apple.com/library/ios/#featuredarticles/FA_Wireless_Enterprise_App_Distribution/Introduction/Introduction.html
This would explain why all wired deployment methods work, but Wireless Distribution always fails. Enterprise developer account is required, it seems. >.<
But, this is not the case! I was able to successfully deploy by completing the following:
You now will have an .ipa file that will work, but in order for the remote-install to register, you will still need the plist file that is generated (and pointed to the new .ipa) for the process to initiate.
So to summarize -- follow enterprise process, then replace generated enterprise .ipa with non-enterprise .ipa
I think it wound up just being a provisioning profile issue. Never REALLY got to the bottom of the exact issue, but I found a great tool that makes the whole process SUPER easy for me: Beta Builder
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With