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

查看:37
本文介绍了info.plist 中的 CFBundleShortVersionString 必须高于 1.0的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在 App Store 上传了应用程序,现在它处于待开发者发布"状态.但我想在发布前将其提供给测试人员.我对内部测试人员没有任何问题,我让他们可以毫无问题地访问应用程序.但是我在使用相同二进制文件的外部测试人员时遇到了麻烦.有错误:

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:

info.plist 中的 CFBundleShortVersionString 必须大于 1.0

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 并且 majorminor 超过 9 时不会增加;相反,版本变为 1.10 直到您对其进行充分的修改以使 major 变为 2 并且 minor 重置为 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 开始递增,这可以使用 this answer 中发布的脚本进行管理.

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

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆