Xcode 6 iOS 应用程序企业分布通过 URL
Xcode 6 iOS app enterprise distribution via URL
我们有一个 iOS 应用程序，它停止安装并出现以下错误：
"Unable to Download App [name] could not be installed at this time"
尝试在任何 iOS 版本 9 设备上安装时。
我使用 Xcode 6 重建 .ipa 文件并使用旧版本的 plist 和 html 文件，但我们仍然遇到相同的错误。我也不知道如何使用 Xcode 6.
重新创建 plist
任何帮助都会很棒
确保根据 Distribution Guide 从 Xcode 正确导出 ipa。确保
select “所有兼容的设备型号”。您还可以 select 在导出时创建新的 plist 清单。
服务器必须在 TLS/SSL 上为 html 网站提供服务。您的证书是否有效且受 iOS 信任？您的服务器支持 App Transport Security 所需的一切，即具有前向保密性的 TLS 1.2。
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).
如果您将 ios 更新为最新的 ios 9.2，问题将得到解决。
谢谢。
我通过创建新的分发配置文件解决了这个问题。在对此进行更多搜索后，我在 Apple 的 iOS 部署参考 (https://manuals.info.apple.com/MANUALS/1000/MA1685/en_US/ios_deployment_reference.pdf)
的第 86 页找到了以下文本
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
似乎每年更新会员后都必须使用新的分发配置文件重新打包该应用程序。
此外，当我使用 Xcode 6 使用新的配置文件重新打包时，此应用程序仍在 iOS 9 上运行。
我们有一个 iOS 应用程序，它停止安装并出现以下错误：
"Unable to Download App [name] could not be installed at this time"
尝试在任何 iOS 版本 9 设备上安装时。
我使用 Xcode 6 重建 .ipa 文件并使用旧版本的 plist 和 html 文件，但我们仍然遇到相同的错误。我也不知道如何使用 Xcode 6.
任何帮助都会很棒
确保根据 Distribution Guide 从 Xcode 正确导出 ipa。确保 select “所有兼容的设备型号”。您还可以 select 在导出时创建新的 plist 清单。
服务器必须在 TLS/SSL 上为 html 网站提供服务。您的证书是否有效且受 iOS 信任？您的服务器支持 App Transport Security 所需的一切，即具有前向保密性的 TLS 1.2。
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).
如果您将 ios 更新为最新的 ios 9.2，问题将得到解决。
谢谢。
我通过创建新的分发配置文件解决了这个问题。在对此进行更多搜索后，我在 Apple 的 iOS 部署参考 (https://manuals.info.apple.com/MANUALS/1000/MA1685/en_US/ios_deployment_reference.pdf)
的第 86 页找到了以下文本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
似乎每年更新会员后都必须使用新的分发配置文件重新打包该应用程序。
此外，当我使用 Xcode 6 使用新的配置文件重新打包时，此应用程序仍在 iOS 9 上运行。