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

查看:429
本文介绍了错误ITMS-9000:“冗余二进制上传。对于列车'1.0'而言,已经存在具有构建版本'1.0'的二进制上载。的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试通过Xcode 5.1.1在iTunes Connect上传我的版本,但这不断显示加载和应用程序没有上传。所以我尝试使用应用程序加载器上传,但显示如下错误:

I am trying to upload my build on iTunes Connect via Xcode 5.1.1 but this continuously showing loading and app is not getting uploaded. So I have tried uploading with application up loader but its showing below error:

错误ITMS-9000:冗余二进制上传。已存在二进制上传为版本'1.0'构建版本'1.0'

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

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

此外,我还检查了vwebsite是否也已更改。不知道出了什么问题。

Also I just checked that vwebsite 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.

推荐答案

可以将多个二进制文件上传到iTunesConnect如果通过添加 .1 来增加每个的Build编号(选择目标,然后是Xcode - > General - > Build,见下图),即如果版本是 3.75 ,然后将其增加到: 3.75.1 3.75.2 等,但版本仍然是 3.75 的应用程序(也在iTunesConnect中)。对于加载到iTunesConnect的每个二进制文件,构建号必须是唯一的。

More than one binary may be uploaded to iTunesConnect if the the Build number (Select the Target, then Xcode -> General -> Build, see the picture below) is increased for each, by adding .1, i.e. if the version is 3.75, then increase it to: 3.75.1, 3.75.2, etc, but the Version remains 3.75 for the App (also in iTunesConnect). The build number just has to be unique for each binary that is loaded up to iTunesConnect.

编辑:在 Xcode 9 之后,如果之前的版本具有相同的版本号,则可能无法上传新版本商店。所以,检查您的内部版本号,如果不确定则增加。

After Xcode 9 you may not be able to upload a new build 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 ,<更正确内部编号的code> 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.

上传并处理新的二进制文件后(约5-20分钟的处理时间,如果它没有再次显示上传并等待),则可以选择新的二进制文件并提交以供审阅。在下图中,您可以在当前应用程序版本的构建部分中看到iTunesConnect中列出的旧二进制文件(单击加号)。然后选择新的二进制文件 - > 已保存 - > 提交审阅。 (有时在提交时出现错误,然后在几分钟后尝试或上传新的​​二进制文件)。

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

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