Install In-House iOS wirelessly using manifest.plist no longer works with iOS 8

We have a distribution scheme inside the house that includes the .ipa and manifest.plist files hosted on the web server. A simple web page allows the user to select the version of the application and click to install it. When a user clicks on a link in Safari on an iPad with iOS 8, he asks if he likes to install the application and do nothing after clicking β€œInstall”. Missing errors or installation progress icon ...

This is the scheme that we used a year before, and I can confirm that it works with iOS 7, as well as with the beta version of iOS 8 (for now, too). It does not work with iOS 8. iOS 8 seems to block it. Has anyone already encountered a problem or knows how to get around it?

The server has MIME types installed:

- application / octet-stream ipa
- text / xml plist

The manifest.plist file is located below:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>items</key> <array> <dict> <key>assets</key> <array> <dict> <key>kind</key> <string>software-package</string> <key>url</key> <string>http://example.com:8079/foo.ipa</string> </dict> </array> <key>metadata</key> <dict> <key>bundle-identifier</key> <string>com.example.fooapp</string> <key>bundle-version</key> <string>1.0</string> <key>kind</key> <string>software</string> <key>title</key> <string>Example Corporate App</string> </dict> </dict> </array> </dict> </plist> 
+3
source share
2 answers

You can also simply change the package identifier in the Manifest.plist file, for example:

 <key>bundle-identifier</key> <string>com.example.fooappNew</string> 

No recovery training profiles.

+4
source

Same problem with my application. Fixed by changing the name of the application package, creating a new application identifier and creating a new provisioning profile.

+1
source

All Articles