简体繁体 English

我们是否需要使用相同的证书和配置文件来分发新应用程序以替换iOS中的旧应用程序？

[英]Do we need to use the same Certificates and Provisioning Profiles to distribute new app to replace old app in iOS?

原文 2016-09-26 06:05:11 3 2 ios/ app-store/ provisioning-profile/ ad-hoc-distribution/ iosdeployment

I am developing an iOS (using Ionic) and it will eventually replace an app currently in App Store. 我正在开发iOS（使用Ionic），它将最终取代App Store中当前使用的应用。 I am using the same app id as the old one. 我正在使用与旧版本相同的应用程序ID。 Do I need the same Certificates and Provisioning Profiles which was used to build old app in order to install new app on top of old app? 为了在旧应用程序之上安装新应用程序，我是否需要使用与用于构建旧应用程序相同的证书和配置文件？ I need to do this both for Ad-hoc and App Store distributions. 对于Ad-hoc和App Store发行版，我都需要这样做。 Thank you. 谢谢。

2 个解决方案

You do not need to use the same certificate to sign your application as long as the app id is the same it will work fine for both Ad-hoc and App store distributions. 只要应用程序ID相同，就不需要使用相同的证书来对应用程序进行签名，它对Ad-hoc和App Store发行版都可以正常工作。

I recently had to create new certificates at work as the old developers didn't have the private keys used to sign the app store builds. 我最近不得不在工作中创建新的证书，因为旧的开发人员没有用于签署应用商店构建的私钥。 You can read more here 你可以在这里阅读更多

For AppStore uploading there is no need for using equal Certificate / Provisioning profile. 对于AppStore上载，无需使用相同的证书/配置文件。 I've changed my certificate and provisioning profile multi times. 我已多次更改证书和配置文件。 This certificate and prov. 此证书和证明。 profile is just for delivering to AppStore. 个人资料仅用于交付给AppStore。

In the case of Ad Hoc as I know, provisioning profile and certificate can be changed by time and it can be replaced just by bundle identifier. 就我所知的Ad Hoc而言，供应配置文件和证书可以随时间更改，并且可以仅由捆绑包标识符代替。 I've tested this for Enterprise licence and new app with new certificate can replace old apps with old certificate. 我已经针对企业许可证进行了测试，带有新证书的新应用程序可以用旧证书替换旧应用程序。