通过URL的Xcode 6 iOS应用企业分发

Question

We have an iOS app, which stopped installing with the following error:

"Unable to Download App [name] could not be installed at this time"

when trying to install on any iOS version 9 devices.

I used Xcode 6 to rebuild .ipa file and used plist and html files from the old build, but we still get the same error. Also I do not know how to recreate plist using Xcode 6 .

Any help would be great

Answer 1

Make sure you properly export the ipa from Xcode, according to the Distribution Guide . Make sure to select “All compatible device variants” . You can also select to create a new plist manifest at the export.

The server has to serve the html website over TLS/SSL. Is your certificate valid and trusted by iOS? Your server has support everything that App Transport Security requires, ie TLS 1.2 with forward secrecy.

Requirements for Connecting Using ATS With ATS fully enabled, your app's HTTP connections must use HTTPS and must satisfy the following security requirements:

The server certificate must meet at least one of the following trust requirements: Issued by a certificate authority (CA) whose root certificate is incorporated into the operating system Issued by a trusted root CA and installed by the user or a system administrator The negotiated Transport Layer Security version must be TLS 1.2 The negotiated TLS connection cipher suite must support forward secrecy (FS) and be one of the following: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA The leaf server certificate must be signed with one of the following types of keys: Rivest-Shamir-Adleman (RSA) key with a length of at least 2048 bits Elliptic-Curve Cryptography (ECC) key with a size of at least 256 bits In addition, the leaf server certificate hashing algorithm must be Secure Hash Algorithm 2 (SHA-2) with a digest length of at least 256 (that is, SHA-256 or greater).

Answer 2

if you update the ios with the latest ios 9.2 the issue will be solved.

Thanks.

Answer 3

I fixed the issue by creating a new distribution profile. After searching more on this, I found the following text on page 86 of in the Apple's iOS Deployment Reference ( https://manuals.info.apple.com/MANUALS/1000/MA1685/en_US/ios_deployment_reference.pdf )

If your distribution certificate expires, the app won't launch. Your distribution certificate is valid for three years from when it was issued, or until your Enterprise Developer Program membership expires, whichever comes first. To keep your certificate from expiring, be sure to renew your membership before it expires.

You can have two distribution certificates active at the same time, with each independent from the other. The second certificate provides an overlapping period in which you can update your apps before the first certificate expires. When you request your second

Looks like the app has to be repackaged with a new distribution profile each year after renewing the membership.

Also this App still worked on iOS 9 when I used Xcode 6 to repackage it using new profile.