确保我总是在升级时覆盖 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?

感谢任何帮助

推荐答案

只要 bundle id 相同，就会覆盖现有的应用.我们为不同的构建配置使用不同的包 ID(一种用于从开发人员的 Mac 构建，一种用于由我们的 CI 盒构建，另一种用于应用商店构建).我们曾经使用一个包 ID，当开发人员构建到设备上时，它会覆盖生产版本(并不总是我们想要的).

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 上进行升级安装)开发密钥).

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屋！