When I try to install an ad hoc build of my app on iOS 8.4 by tapping an itms-services:// URL in Safari, nothing happens. This appears in the iOS device console:
Jun 30 23:30:34 Jeff-Hunters-iPhone-5s itunesstored[586] <Warning>: ExternalDownloadManifest: Skipping download and install of: com.purplecover.anylist
That is the only information provided. This worked fine before. Anyone know what changed in iOS 8.4?
Got it working again. In the manifest plist, rename the bundle-identifier under metadata to anything but the actual bundle identifier.
I just added '.dummy' and it installed fine again on iOS 6, 7, 8 and 9.
Still testing so not sure if this has any side effects...
I'm getting a similar issue. I get the same message in the Console Log
Jul 15 17:09:44 Christopher-Princes-iPad-Air itunesstored[103] <Warning>: ExternalDownloadManifest: Skipping download and install of: biz.SpasticMuffin.Petunia
I just tried the suggestion of changing the .plist file:
<key>bundle-identifier</key>
<string>biz.SpasticMuffin.Petunia.dummy</string>
and no change. In fact, the message in the Console Log doesn't change. Which I find odd.
This issue is arising only when there is a prior app store installed build present on the device. If I delete the build on the device, the OTA installation works as normal. This is not a huge problem for me, except that I'm trying to do a testing step where I want to make sure my new app release works when installed over top of the old app release.
I faced this issue. iOS 9 validates the bundle id. If bundle id mentioned in entilement.plist doesn't match with app's bundle id, then iOS 9 wont allow the installation. This bundle id validation seems to be introduced in iOS 9. Please check your bundle id in entitlement.plist and app's info.plist. If you find any discrepencies, then change that id to make identical.
I was observing this on iOS 9 as well. After removing the previous ad hoc build, it is working again now. I guess this is because I previously used the ".dummy" identifier fix that was helpful during iOS 8.x times.
This lead me to getting things fixed, thanks!! I guess in iOS8 it didn't validate the case of the bundle id
i does work this way when an AppStore Version of this app is not installed on the device. If you try to install an AdHoc Version (to test an AppUpdate) over an installed AppStore Version nothing happens. Any suggestions?
Yup, I just wasted several hours due to this same problem.
When an App Store version of your app is installed on your device, and you try and install an Ad-Hoc version on top (even with a later version number), then the device just ignores it. Nothing gets installed, nothing appears on the screen, but it quietly logs that message.
<Warning>: ExternalDownloadManifest: Skipping download and install of: com.purplecover.anylist
Why would you not display an error message, when your device has decided to ignore such an install ?
This really is Apple at its very worst.
I wasted further hours due to my Provisioning Profiles being marked as "Invalid (managed in Xcode)". The solution was to delete our perfectly valid "iOS Distribution" certificates and recreate them. And yet more hours trying to get around misleading In-House install errors which were actually caused by the
"Apple Worldwide Developer Relations Certification Authority" having expired. Once again, Apple knew about this issue, and made no effort to help developers who got stuck by it. No useful error messages appear, you're just expected to burn hours, Google what little messages you can find in the log, and hopefully stumble across the problem that their expired certificate has caused.
Imagine if us develoers decided to follow Apple's example.
"Ahhh, my iPad app can't contact its web service. Let's just silently add a log entry which the user won't be able to see, show nothing on the screen, and leave the user to wonder what's just happened."
If an error has occured, report it to the user. It's common sense.
Oh, and another one I've hit today.
Our company has an iPad app in the App Store, but strangely, the App ID identifier had disappeared in the "Certificates, Identifiers and Profiles" screen, so I can't build a new version using this same App ID. If I try to create a new App ID with this ID, I get an error of "An App ID with Identifier 'com.mycompany.myappname' is not available. Please enter a different string."
Once again, this is Apple's error handling at its worse. Actually, what the problem is is that Apple has changed its rules. Now, the app ID *must* be com.mycompany.myappname.somethingelse. Does the error message give any hint that this is what's causing the problem ? Of course not. Once again, you're left baffled as to what Apple has broken/changed this time, and left Googling to fiind other victims with the same issue.
I hate Xcode. Every year. Every release.
It just keeps getting worse.