确保我总是在升级时覆盖ios应用 [英] Ensure I always overwrite ios app on upgrade

问题描述

我将要启动我的应用程序的更新，该更新以前是由单独的开发人员构建的.我想确保将应用程序迁移到团队中，但是我需要确保发布的应用程序将升级用户现有的应用程序，而不安装新的应用程序.我使用的是相同的应用程序标识符，但是我还需要使用相同的证书和配置文件吗?

I am about to launch an update to my app that was previously built by a separate developer. I want to make sure that I transition the app to my team however I need to make sure the app I publish will upgrade the users existing app and not install a new one. I am using the same app identifier but do I also need to use the same certificate and provisioning profile?

感谢您的帮助

推荐答案

只要捆绑包ID相同，它将覆盖现有应用程序.我们为不同的构建配置使用了不同的捆绑包ID(一个用于从开发人员的Mac进行构建时使用，一个用于通过CI框进行构建时使用，另一个用于应用商店构建时使用).我们曾经使用一个捆绑软件ID，当开发人员在设备上构建产品时(它并不总是我们想要的)，它将覆盖prod构建.

As long as the bundle id is the same, it will overwrite the existing app. We use different bundle IDs for our different build configurations (one for when it is built from a developer's Mac, one from when it is built by our CI box, and one when we build for the app store). We used to use one bundle ID, and it would overwrite the prod build when a developer built to the device (not always what we want).

您可能正在考虑使用Android，如果您的APK签名不同，Android的行为也会有所不同.我相信它仍然会取代现有的应用程序，但是它将迫使您首先进行卸载，因此，如果这些应用程序的签名方式不同(即，一个应用程序使用发行密钥安装，而另一个应用程序使用发行密钥安装，则无法在Android上进行升级安装)开发人员密钥).

You may be thinking of Android, which will behave a bit differently if you have your APK signed differently. I believe it will still replace the existing app, but it will force you to do an uninstall first, so you cannot do an upgrade install on Android if the apps were signed differently (i.e. one app is installed with your distribution key, the other with a dev key).

这篇关于确保我总是在升级时覆盖ios应用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！