I\'ve followed all the directions from Apple and some other blog posts. I\'ve archived the app, made .plist and .ipa files, put them on a server and linked to them. I can in
I tried some at the same time, so I'm not sure which one was the good one.
Created a wildcard app id (name wildcard, bunde identifier *), created a profile for this app and signed the ipa with this profile.
Registered one device on the provisioning portal.
named the file where I linked the app dev.html instead index.html
For anyone who is interested in dynamically generating their plist, this example is PHP:
$appUrl='itms-services://?action=download-manifest&url=http://server/iOSpList.php?'.
'url%3D'.$app['url'].
'%26bundle%3D'.$app['bundle'].
'%26version%3D'.$app['version'].
'%26name%3D'.$app['name'];
Also, make sure the mime type is returned as application/xml
.
I think you also need to make it https, as in https://mydomain
I had the same problem as above. After trying all of the above and failing, I figured out that when I was archiving my app, I didn't put in the application URL in the settings, thus this URL was never in my plist file. Make sure when you look at your plist file that the application URL is in there.
itms-services is an identifier by which apple/iphone will identify that it should validate the certificate and it should install.
To validate the provisioning profile before installing the ipa file it will connect to "ax.init.itunes.apple.com" and "ocsp.apple.com".
If you are using any intranet connection please check whether these links are accessible or not? if not, you cannot install the application via over the air.
& minimum OS on the device should be 4.0
I had similar symptoms when I had a space in the filenames of the manifest file and the application archive file. I removed all spaces from them and the wireless install worked for me. It looks like your manifest doesn't have a space, so maybe your app file does?