错误 ITMS-9000:“冗余二进制上传.已经存在一个编译版本为“1.0"的二进制文件上传，用于训练“1.0"". [英] ERROR ITMS-9000: "Redundant Binary Upload. There already exists a binary upload with build version '1.0' for train '1.0'"

问题描述

我正在尝试通过 Xcode 5.1.1 在 iTunes Connect 上上传我的构建，但它不断显示它正在加载并且应用程序没有被上传.所以我尝试使用 Application Loader 上传，但显示以下错误:

I am trying to upload my build on iTunes Connect via Xcode 5.1.1 but it is continuously showing that it is loading and app is not getting uploaded. So I have tried uploading with Application Loader but its showing the below error:

错误 ITMS-9000:冗余二进制上传.已经存在一个编译版本为 '1.0' 的二进制文件上传，用于训练 '1.0''

ERROR ITMS-9000: "Redundant Binary Upload. There already exists a binary upload with build version '1.0' for train '1.0'"

iTunes 上的应用程序状态为等待上传.有一次上传成功，但状态没有反映，现在允许再次上传.

App status on iTunes is Waiting for Upload. One time the upload was successfully done, but the status is not reflecting and it's now allowing to upload again.

此外，我刚刚检查了该网站也已更改.不知道怎么回事.

Also I just checked that website is also changed. Don't know what's wrong.

苹果新网站上没有提交审核按钮.但是现在我可以看到那个按钮了.这已经解决了我的问题.此外，我建议使用 Application Loader 上传构建，因为它比管理器更快.

There was no submit for review button on apples new website. But now I can see that button. That has solved my issue. Also I recommend to upload the build using Application Loader as it's quicker than organizer.

推荐答案

如果每个版本的 Build 编号都在增加，同一版本的 App Store Connect 可能会上传多个二进制文件上传到 iTunesConnect.对于每个上传的二进制文件，版本号必须唯一(或更高)(选择目标，然后选择 Xcode -> General -> Build，见下图).例如，在下图中，上传的构建版本具有版本 3.1.4(旧图像中的 3.75)并且构建编号为 1.因此，在上传此图像后将构建增加到至少 2 或更高.然后这个二进制文件也可以上传到 App Store Connect，因为它是根据 build number 的后续版本.

More than one binary may be uploaded to App Store Connect for the same version, if the the Build number is increasing for each build uploaded to iTunesConnect. The build number just has to be unique (and higher) for each binary that is uploaded (select the Target, then Xcode -> General -> Build, see the picture below). For example in the image below the build uploaded has version 3.1.4 (3.75 in the older image) and the build number is 1. Thus, after uploading this image increase the build to a minimum 2 or higher. Then this binary may also be uploaded to App Store Connect as it's a later build according to the build number.

version 注明您向用户发布的应用发布版本.build number 表示上传到商店的二进制文件的最终 build，即在许多错误修复之后.

The version notes the release version of the app your releasing to the user. The build number remarks the final build of the binary uploaded to the store, i.e. after many bug fixes.

在 Xcode 9 之后，如果商店中存在具有相同版本号的先前版本，您将无法上传新版本(对于相同版本).因此，请检查您的内部版本号，如果不确定则增加.

After Xcode 9 you are not able to upload a new build (for the same version), if there is a previous build with the same build number in the store. So, check your build number and increase if not certain.

使用 1、2、3、4 等更正确内部版本号，但版本号必须增加，1.0 -> 1.1 -> 1.2 等等.内部版本号必须高于之前为相同版本号提交的版本号，如果没有发布错误.因此，如果提交了版本为 3.75 的新二进制文件并且已经提交了构建 1，那么下一个构建应该是 2 或更高版本，但版本仍然可以保持为 3.75.

It's more correct to use 1, 2, 3, 4, etc. for the build number, but the version number has to be increasing, 1.0 -> 1.1 -> 1.2 etc. The build number has to be higher than what was submitted previously for the same version number, if not an error is posted. So, if a new binary is submitted that has version 3.75 and a build 1 has already been submitted, then next build shall be 2 or higher, but the version can still remain 3.75.

新的更新和推荐的内部版本号序列方式:

与以下图片相匹配的旧图片:

The older image to match the one below:

在上传并处理新的二进制文件后(大约 5-20 分钟的处理时间，如果它没有再次显示上传并等待)，那么您可以选择新的二进制文件并提交以供审核.在下图中，您可能会在当前 App 版本的 Build 部分中看到 App Store Connect 中列出的旧二进制文件和新二进制文件(单击加号).然后选择新的二进制文件 -> Saved -> Submit for Review.(有时提交时会出现错误，然后几分钟后尝试或上传新的​​二进制文件).

After a new binary is uploaded and processed (~5-20 min processing time, if it doesn´t show up upload again and wait), then you can select the new binary and submit it for review. In the picture below you may see the old and the new binary listed in App Store Connect in the Build section of the current App version (you click the plus sign). Then the new binary is selected -> Saved -> Submit for Review. (Sometimes an error comes when submitting, then just try after a few mins or upload a new binary).

对于那些倾向于使用 Xcode 脚本自动执行此操作的人，这里是制作用于更新内部版本号的自动脚本的说明 增加内部版本号的更好方法?

For those inclined to do this automatically with an Xcode script, here is a description of making an automatic script for updating Build numbers Better way of incrementing build number?

这篇关于错误 ITMS-9000:“冗余二进制上传.已经存在一个编译版本为“1.0"的二进制文件上传，用于训练“1.0"".的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！