8

For all prior versions of iOS, I've used the itms-services:// URL to install test iOS apps over the air (OTA). Now, all my devices with iOS8 fail when trying to install apps using this approach. Example URL:

itms-services://?action=download-manifest&url=https://myWebsite/myApp/myApp.plist

Summary of problem:

  1. The Safari browser used to launch the install from a web page does not exit to the main screen showing the app installing as before in prior iOS versions
  2. The application never successfully installs. It installs, but is left as a greyed out icon, and the app will not launch.
  3. This problem does not occur on existing iOS7 devices, with identical URL.
MStudios
  • 1,073
  • 1
  • 12
  • 14
  • Possibly related? http://stackoverflow.com/questions/25772664/enterprise-app-update-distribution-on-ios-8 – ahruss Sep 18 '14 at 22:17
  • I've just tested my app via testflightapp and it works fine.If I'm not wrong that service uses the same distribution way. – razor28 Sep 19 '14 at 08:20
  • have you looked at the console output to see what (if any) errors are being reported? I've used this method to track down issues with the `itms-services` manifests a few times in iOS7 and it was very helpful – liamnichols Sep 19 '14 at 08:34

5 Answers5

8

This seems to be a bug in the Beta5 and GM versions of iOS8.

Over at Buildozer we've found a workaround: change the bundle identifier of the app in the manifest file. (More details: https://buildozer.io/ios8)

A workaround that doesn't involve changing the manifest files is to restore the entire device from backup, however we feel the manifest 'hack' is less disruptive to users.

Ivo Jansch
  • 1,438
  • 1
  • 15
  • 18
  • 1
    No, it's unfortunately NOT fixed with iOS 8.0.2 - I'm still able to reproduce the error on that release. – Peter Theill Oct 01 '14 at 05:38
  • Hi. Had a look at the link above, https://buildozer.io/ios8. it indicates adding -iOS8 "somewhere". Could you be more specific, is the itms link used to download the ipa file or the plist file itself? I have this issues. I have 160 people that are in a mixed state. Some running iOS8.1 and lower, some that can and cannot download our App. Very strange. No pattern other than phones are largely ok, but iPads are in the main, the problem. Help? – Carl Hine Oct 30 '14 at 16:41
  • Still not fixed in 8.1.3... Thanks for the workaround – Dulgan Feb 19 '15 at 14:30
7

This answer helped me to fix the issue. It seems that for iOS8 you have to include in the assets key of the manifest .plist file the display-image and full-size-image keys. They were available in Xcode 5 when saving an archive for enterprise and add-hoc deployment, but not required.

I have created a gist on github with the template for the install-manifet.plist file. The original post is available on http://www.informit.com/articles/article.aspx?p=1829415&seqNum=16.

Community
  • 1
  • 1
alexcristea
  • 2,316
  • 16
  • 18
4

As far as we know, this issue still not be solved in iOS 8.1, and we found that this solution will cause some side effect. After iOS 7.0.x devices use this method to install inHouse apps, although the app installed successful but the home screen left a black square, and can't be deleted.

You have to separate the install method between iOS8 and other iOS versions, which means you change the install method in iOS8, and keep the original install method in other version.

Elan Wang
  • 121
  • 5
3

I had the same problem. In my case the problem was fixed when:

  • the plist was served from HTTPS
  • the IPA was served from HTTPS from the same domain as the plist
  • full-size-image and display-image are present in the plist
wasigh
  • 895
  • 1
  • 11
  • 21
0

We had the same problem. Our cause was that TestFlight had installed the bundle previously. It seems that TestFlight has (had) a profile installed, and only it could update the apps, even if they were uninstalled and deleted.

A workaround was to add some suffix to the bundle identifier in the plist.

This of course caused another problem, that a secondary icon was showing until download was complete and the IPA was unpacked and matched with the app already on device.

BIG NOTICE: This is only a problem with iOS8, so you better check the user-agent during the download. It will be itunesd and will contain the exact iOS version.

gilm
  • 7,690
  • 3
  • 41
  • 41