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

Question

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:

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

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.

---

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.

Solution 1

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.

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.

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.

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.

New updated and the recommended way 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).

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?

Solution 2

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

The standard way in my opinion is to put an integer in build number and a float or dotted string for version.

i.e.

     Version: 1.0.0
     Build: 2

Solution 3

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

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.

Solution 4

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.

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.

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!

Solution 5

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!

Screen Shot of my settings:

View more solutions

Comments

[Sovannarith]

Apple so crazy now. Ituneconnect website also change. I stucked 1hour to look around of this website for updating new version of my app.

[Dhara]

@chhi were you able to upload the build to itunes?

[Brennan]

I am experiencing the same problem. I had to reject my binary after we found a problem which I fixed and tried to upload the replacement binary. I've logged it with the Apple Bug Reporter. (#18257715). Please go let the know you are also having this problem so they prioritize it.

[Sam]

I want to upload 1.01 not 1.02. What should i do now?

[neelabh]

I am having the same problem. Although I have two build and no submit for review button. Did you actually get submit for review button after clicking the 1.4 build of yours?

[Alpesh Patoliya]

@neelabh yes its seem waiting for review. after uploading 1.4

[Alpesh Patoliya]

@user28 for update version, you will need to change version. make it 1.02

[Brennan]

Thanks, I managed to get past this error by changing my build number to use format, YYYYMMDDhhmm, which I can update each time I push a new build to the App Store with the current date and time. I would like to automate the build number change though.

[Sverrisson]

@Brennan I added a link to instructions on making Build numbers increase automatically.

[Simon]

@HannesSverrisson what do you recommend for those of us who already use three parts in our version numbers?

[Sverrisson]

@Simon I guess that you would have to add the build as the fourth part. The client will never see the build number in the App Store.

[Simon]

@HannesSverrisson but we're no longer allowed to use a fourth part!

[Sverrisson]

@Simon, sorry I did´t know that. So, I guess, the only way for you is too review your numbering policy. You might have the last part two digits 01 and then the build in Hex 0A, then last part is 010A etc.

[Genki]

The problem is that some libraries and frameworks use the build number as the version number.

[Ekra]

So what you did when you got "Redundant Binary Upload". Because I got the similar mail from Apple and my application is showing "Waiting for review"

[d1jhoni1b]

In my case i think this is the reason i do see my all of my uploads at "builds" tab at itunes connect...even though i have being waiting for 50 minutes and still nothing...hopefully in the following hours ill get my builds enable on versions tab so i can submit for review

[d1jhoni1b]

In my case this took more than 45 minutes but this was the main reason it seems there is a huge delay between each time you upload from XCode to iTunes connect

[aroth]

Apple used to let you manually clean up any unwanted binaries. Looks like not anymore, as they've decided to key off of the build number that's set in the .plist file.

[Adil Malik]

For me just three level version number worked. The only thing I noticed is that 1.1.0 is treated as 1.1. So, I had to try 1.1.1 instead of 1.1.0

[Simon Tillson]

I totally agree. All these people using the same number for both fields are really missing the point. Version number is the public version you are hoping to release. Build number is the internal, well, build number! It goes up each time you build your app for testing, so you have a reference to bug track it which changes whenever the code does. This is why test flight lists your builds the way it does. Eg. Version 1.0.0 (2) It depends on your company how you structure the build number. Sometimes, testing stages require separate levels, so floats are fine too really.

[Pradeep Mittal]

What about this issue ? prntscr.com/8xcu7o Please notice the build still processing when its already 3 days since the build is uploaded.

[DawnSong]

I can not agree with you more. You will find that it's Xcode's default strategy if creating a totally new project.

[dang]

the weird thing is that even if you delete your first binary uploaded and try to upload a new one, you will get this error unless you increase the build.

[Sverrisson]

@dang You can't delete the first binary from Apples servers, it's still there. You can check by re-adding the previous binary.

[AnBisw]

As of xcode 9, the binary build doesn't even have to be uploaded to iTunes connect, if a redundant build exists in you Archives list in the local machine Xcode will yell at you.

[AnBisw]

@HannesSverrisson actually, what I wrote isn't correct. There was a delay in the build showing up in iTunes connect. And I was uploading the same build again and that's why it gave an error. There no need to delete the builds from the archive list.