将两个独立的应用程序更新为单个通用应用程序？
我们目前有两个独立的应用程序（一款仅 iPhone 和一款 iPad），并且希望迁移到单个通用应用程序。
有谁知道是否可以在不杀死其中一个应用程序的情况下做到这一点？比如向每个应用程序发布包含相同二进制文件的更新？
如果我在某处遗漏了这个答案，请链接，谢谢！
We currently have two independent apps (one iPhone only and one iPad only) and want to migrate to a single universal app.
Does anyone know if it is possible to do this without killing off one of the apps? Someting like releasing an update to each app, containing the same binary?
Please link if I'm misssing this answered somewhere, thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
目前没有办法做到这一点，除非孤立其中一个应用程序，或继续支持两个几乎相同的应用程序。您无法发布相同的二进制文件，因为每个应用程序都有一个嵌入在二进制文件中的不同的、不可更改的唯一应用程序标识符。
一些开发人员只是将应用程序留在应用程序商店中类别中最不理想的评论、评级和受欢迎程度，而没有进行任何进一步的升级。您可以执行一些操作，例如将要留下的名称更改为“foo classic”或“foo Legacy”，以及为支持的较新应用程序添加一些不显眼的广告。
There is no current way to do this except by orphaning one of the apps, or continuing to support two nearly identical apps. You can't release identical binaries because each app has a different unchangeable unique App Identifier for that app embedded in the binary.
Some developers just leave behind the app with the least desirable set of reviews, ratings and popularity in category in the app store without any further upgrades. You could do something like change the name of the one you want to leave behind to "foo classic" or "foo legacy" as well as add some unobtrusive advertisements for the supported newer app to it.
App Store 根据 App ID 跟踪应用程序。如果它们都是免费应用程序，则删除最不受欢迎的应用程序。但如果他们都是付费的，那么如果你让客户再次购买该应用程序，你可能会疏远他们，因为你正在合并他们。
App Store tracks application based on the App ID. If they are both free apps, just kill off least popular one. But if they are both paid, you can alienate your customers if you make them purchase the app again because you are merging them.
手机上的应用程序基础架构通过 ID 来跟踪应用程序，并且一个应用程序只能有一个 ID。快速的方法是孤立其中一个应用程序，另一种方法是调整您的构建过程，以便当您进行分发构建时它会生成两个捆绑包，除了 info.plist 文件之外，两者都是相同的。
The app infrastructure on the phone tracks apps by ID and an app can only have one ID. Quick way would be to orphan one of the apps, another way would be to tweak your build process so that when you do a distribution build it generates two bundles, both identical except for the info.plist file.