我应该避免为新版本更改 iOS 应用程序的 CFBundleName 吗? [英] Should I avoid changing the CFBundleName of my iOS app for a new release?

问题描述

我有一个已经发布的 iOS 应用程序，它的 Info.plist 中有一个特定的 CFBundleName.

I have an already released iOS app with a certain CFBundleName in its Info.plist.

为了更新，出于一致性原因，我更改了 CFBundleName(以及生成的 .app 产品的名称).这对用户是不可见的，他们只能看到 CFBundleDisplayName.

For an update, I changed the CFBundleName (and hence, the name of the generated .app product) for consistency reasons. This is invisible to the user, who only sees the CFBundleDisplayName.

但是，客户端设备上的更新似乎无法正常工作 - 更新进度条到达末尾，跳回到开头，然后停止.唯一的解决办法是删除并重新安装该应用.

However, it seems that the updates on clients’ devices don't work correctly — the update progress bar reaches the end, jumps back to the beginning, and stops. The only solution is to delete and reinstall the app.

所以:

• 是否禁止更改现有应用的 CFBundleName?
• 是不是破坏了我的更新?
• 如果是这样，为什么 Apple 的验证过程没有对此进行检查?

推荐答案

两年后，我用一个最佳答案来回答这个老问题:不，人们不应该特别避免更改 CFBundleName.

After two years, I am answering this old question with a best-guess answer: no, one should not especially avoid changing the the CFBundleName.

这篇关于我应该避免为新版本更改 iOS 应用程序的 CFBundleName 吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！