Month: September 2014
If you are having following issue on new interface of iTunesConnect
“Redundant Binary Upload. There already exists a binary upload with build version ‘1.0’ for train ‘1.0’”
then you are not alone like forever alone guy. Like me and you, many others are facing this issue. But no worries, the solution is pretty simple.
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 by adding
.1, i.e. if the version is
3.75, then increase it to:
3.75.1, but the Version is still `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.
After a new binary is uploaded and processed (~ 10 min), 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 ->
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?
Note: The content of this post is extracted from this question over stakeoverflow.