info.plist中的CFBundleShortVersionString必须高于1.0 [英] CFBundleShortVersionString in info.plist must be higher than 1.0

问题描述

我在App Store上传了应用程序，现在它处于Pending Developer Release状态。但我希望在发布之前将它交给测试人员。我没有内部测试人员的麻烦，我给他们访问应用程序没有问题。但是我对使用相同二进制文件的外部测试人员有困难。有一个错误：

I uploaded the app in App Store, and now it in "Pending Developer Release" status. But I want give it to testers before release. I have no troubles with internal testers, I gave them access to application without problems. But I have trouble with external testers with the same binary. There is an error:

"CFBundleShortVersionString in info.plist must be higher than 1.0"

如果我不想重新加载二进制文件，我该怎么办？因为我可能会失去待定开发者版本状态？

What should I do, if I don't want to reload binary, because I can lose the "Pending Developer Release" status?

推荐答案

当您使用Apple的分发系统（即App Store或TestFlight）发布新版本时，版本号需要高于之前的版本。

When you release a new version using Apple's distribution system (i.e. App Store or TestFlight) the version number needs to be higher than the previous release.

如果应用程序仍在测试中，它甚至不应该达到 1.0 。从 0.1 开始，并在达到开发里程碑时递增至 0.999 。一旦经过测试并准备发布，请将其设为 1.0 。无论如何，这是我对这个问题的看法;实际值并不重要，但是有些用户可能会查询新发布的应用程序为什么版本号 1.452 ，例如。

If the app is still in testing, it shouldn't have even reached 1.0 yet. Start with 0.1 and increment up to 0.999 as development milestones are reached. Once it's tested and ready for release, make it 1.0. This is my thinking on the issue anyway; the actual value is not important, however some users may query why a newly-released app has a version number of 1.452, for example.

请注意，该数字不是浮点数;而 major.minor 和 major 在 minor 超过9;相反，版本变为 1.10 ，直到你做足够的工作， major 变为 2 和次要重置为 0 ，依此类推。

Note that the number is not a floating point; instead it's major.minor and major does not increment when minor goes above 9; instead the version becomes 1.10 until you rework it sufficiently that the major becomes 2 and the minor resets to 0, and so on.

因此，要回答您的问题，请将 CFBundleShortVersionString 更改为 1.1 。

So to answer your question, change CFBundleShortVersionString to 1.1.

至于 CFBundleVersion ，这应该是一个整数，每当构建时从 1 递增已执行并且源文件已更改（在我看来也是如此），可以使用此答案。

As for CFBundleVersion, that should be an integer that increments from 1 whenever a build is performed and source files have changed (again, in my opinion), which can be managed with a script as posted in this answer.

这篇关于info.plist中的CFBundleShortVersionString必须高于1.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！