ios 错误 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'"

提问by Dhara

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:

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

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

错误 ITMS-9000：“冗余二进制上传。已经存在构建版本为 '1.0' 的二进制上传，用于训练 '1.0'”

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

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

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

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

EDIT

编辑

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.

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

回答by Sverrisson

More than one binary may be uploaded to App Store Connectfor 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.

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

The versionnotes the release version of the appyour releasing to the user. The build numberremarks the final buildof the binary uploaded to the store, i.e. after many bug fixes.

该version注意到应用程序的发布版本的发布给用户。该build number言论最终构建上传到店，即许多bug修复后的二进制。

After Xcode 9you 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.

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

EDIT: 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.

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

New updated and the recommendedway of having the build numbers serial:

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

The older image to match the one below:

与以下图像相匹配的旧图像：

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).

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

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?

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

回答by atulkhatri

I don't know why people are putting a floatin build number.

我不知道为什么人们要float输入内部版本号。

The standard way in my opinion is to put an integerin build number and a floator dotted stringfor version.

在我看来，标准的方法是把一个integer在建数量和float或dotted string换版。

i.e.

IE

     Version: 1.0.0
     Build: 2

回答by ALPESH PATOLIYA

You will need to just change the Build and Its version. In store live version : 1.1 For upload new version : 1.2 (Here if you fail to upload with 5.1.1 or earlier version) then again need to upload so New upload will be : 1.3

您只需要更改 Build 及其版本。In store live version : 1.1 For Upload new version : 1.2 (这里如果你用5.1.1或更早版本上传失败)然后再次需要上传所以新上传将是：1.3

Now go iTunesconnect account login Apps> Select your app > In Build section remove old by click on (-) again select by click (+) here you see all build select last one then Done, Save it then submit for review. Also check attached screenshot.

现在转到 iTunesconnect 帐户登录应用程序> 选择您的应用程序 > 在构建部分删除旧的，通过单击 (-) 再次通过单击 (+) 选择这里您会看到所有构建选择最后一个然后完成，保存它然后提交以供审核。还要检查附加的屏幕截图。

回答by Kibernetik

Definitely it is not possible to delete old build from iTunes Connect before uploading its newer version. iTunes Connect interface is just not as advanced for this operation.

在上传较新版本之前，绝对不可能从 iTunes Connect 中删除旧版本。iTunes Connect 界面对于此操作来说并不先进。

But actually you don't need to delete it (let Apple take it for themselves if they like). You need to change your Build number(not Version number) and upload it again.

但实际上你不需要删除它（如果他们愿意，让 Apple 自己拿走）。您需要更改内部版本号（不是版本号）并再次上传。

For example if you have Version number 1.0 with Build number 1.0 then change Build number to 1.0.1 and leave Version number as it is 1.0. Then upload it - and iTuned Connect will accept newer build. All the rest is quite obvious. Good luck!

例如，如果您的版本号为 1.0，版本号为 1.0，则将版本号更改为 1.0.1，并将版本号保留为 1.0。然后上传它 - iTuned Connect 将接受更新的版本。其余的都是很明显的。祝你好运！

回答by user3730468

I tried increasing the build number out to 3 decimals (eg. 1.5.1) and that still got me the redundant binary error. After I added one more decimal (eg. 1.5.1.0) it worked!

我尝试将内部版本号增加到 3 位小数（例如 1.5.1），但这仍然给我带来了冗余的二进制错误。在我再添加一位小数（例如 1.5.1.0）后，它起作用了！

Screen Shot of my settings:

我的设置的屏幕截图：

回答by kees

I noticed that Apple takes a lot of time before a build becomes available for submission. I uploaded my build a couple of times before I could select it. By than my build was invalid because the same build version was a couple of times on the server and I got the "Redundant Binary Upload" mail.

我注意到 Apple 需要花费大量时间才能提交构建版本。在我选择它之前，我上传了几次我的构建。比我的构建无效，因为相同的构建版本在服务器上出现了几次，并且我收到了“冗余二进制上传”邮件。

In my case I could select the new binary 15 minutes after uploading the build (with new build number) form Xcode.

在我的情况下，我可以在从 Xcode 上传构建（带有新的构建号）后 15 分钟选择新的二进制文件。

回答by nalexn

I need to warn you that almost all answers here (including accepted one) promote non-conventional way for numerating builds.

我需要警告你，这里几乎所有的答案（包括被接受的答案）都提倡用非常规的方式来计算构建。

This is not critical, but it's always better to stick with convention, so I encourage you to check out this answerto get an idea on how to numerate your builds.

这并不重要，但坚持约定总是更好的，所以我鼓励您查看这个答案以了解如何计算您的构建。

And yes, answering the original question, all you have to do is to increment your build number. Properly.

是的，回答最初的问题，您所要做的就是增加内部版本号。正确。

回答by Rodney Gracia

I just went through the same issue. Unfortunately I had created version 1.0.1 of my app and uploaded a binary with the same version which got rejected as invalid. There was no way for me to reject the binary from the system afterwards so I had to first figure out what the reason for the rejection was and then change the app version to 1.0.2 on both iTunes Connect and the new uploaded binary with the correct code fixes. It is now sitting at Waiting for Review.

我刚刚经历了同样的问题。不幸的是，我创建了我的应用程序的 1.0.1 版本并上传了一个具有相同版本的二进制文件，但由于无效而被拒绝。之后我无法拒绝系统中的二进制文件，所以我必须首先弄清楚拒绝的原因是什么，然后在 iTunes Connect 和新上传的二进制文件上将应用程序版本更改为 1.0.2代码修复。它现在坐在等待。

The first 3 times I attempted this, the binary was rejected almost immediately. It took me about 2 hours to figure out my rejection reason which was to remove 'arm64' from the Valid Architectures. I hope this helps you.

在我尝试此操作的前 3 次时，该二进制文件几乎立即被拒绝。我花了大约 2 个小时才弄清楚我的拒绝原因，即从有效架构中删除“arm64”。我希望这可以帮助你。

回答by stebooks

I simply increased the version number first inside of iTunes connect. This allowed me to upload a new version of the binary and had no problems.

我只是在 iTunes Connect 中首先增加了版本号。这使我可以上传新版本的二进制文件并且没有问题。

回答by codingFriend1

I wanted to upload version 2.4of my app and got exactly that error message. This was the first upload of the version and there was definitely no binary existing on iTunesConnect.

我想上传2.4我的应用程序的版本并收到了该错误消息。这是该版本的第一次上传，iTunesConnect 上绝对没有二进制文件。

I could easily solve this by changing the build version from 2.4to 2.4.0. There is no need to increment the version. I guess iTunes just expects a three-part version number for the build version.

我可以很容易地通过更改内部版本解决这个2.4来2.4.0。不需要增加版本。我猜 iTunes 只需要构建版本的三部分版本号。