Getting ITMS-4238 “Redundant Binary Upload” error

Question

I rejected a binary i had which was 1.0 (1.0). The status went into Rejected by developer.

I went to upload a new binary and ran into this issue, i then saw that i needed to increment my build.

I increased both the app version and build to 1.1, this was a mistake.

I got some error about the app version not matching, understood.

Then i tried app version 1.0 and many different build numbers. 1.1, 1.0.1, 1.2, 1.3, 1.0.3..nothing works. I keep getting this error. There is only one build listed on itunes connect (1.0)

I tried submitting with no binary and it says i need one.

I even tried changing the app version to 1.1 in itunes connected and then uploading 1.1 (1.0) and that fails as well with the same duplicate issue.

Anyone ever have this issue?

Answer 1

For certain reason, Apple provided the build field on the General Tab in Xcode.

I have also encountered this issue and as much as you do, I am getting the same error over and over again even if I was changing the version numbers.

What is suppose to be done here is to update the build number only even using the same version number.

In my case, I have an App version 0.0.1, every time I upload a binary I need to change the build number eg: Upload build 0.0.0 - Reject Binary and Upload build 0.0.1 - Reject Binary and Upload build 0.0.2

Answer 2

Check if you have used the run script:

if the answer is yes, then you have to submit your changes to your git server, then the script will increase your build version number automatically!

Answer 3

Solved this issue by incrementing build version by 1 instead of sub-version. i.e. 1.0 to 2.0 instead of 1.0 to 1.1

Answer 4

I was trying for hours with no luck, after waiting a few more hours i got a reply from apple support asking for more info. When i went to replicate the issue again for screenshots i decided to use a build number of 2.0, i was hoping maybe it wanted the major version to be higher. This worked! Everywhere online that i read said that 1.0 to 1.1 would work fine...or 1.0.0 to 1.0.1. I, for some reason, had to go from 1.0 to 2.0.

Or there is always the possibility that waiting a few more hours did something.

Answer 5

Solved this problem by Modifying the Build Number under General -> Identity in the Target build of the Xcode project. Afterwards go to the Product menu, select Clean and Build your app.

From Build : 1
To Build   : 1.2

Finally, repeat the app submission process by running Product -> Archive and follow the screen prompts.

Answer 6

The workaround of changing the build number is working for me, with the following context:

• the app version status is "Prepare for submission"
• the new version number is well saved in iTunesConnect (pressing the save button on version page in iTunesConnect)
• the CFBundleShortVersionString is matching the version number in iTunesConnect (e.g. "1.2")
• the CFBundleVersion in the Info.plist is incremented (e.g. 1.2.1)

In this way, several build are associated to the iTunesConnect version.

Here is how it looks like in iTunesConnect (1.2 is the short version number, 1.2 and 1.2.1 are the bundle versions):