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

I've had this problem before and have solved it like you have, by upping my build number every time. It has always worked.

Now however, I am completely stuck. I have just added the Today Extension to my app, and now when I try to upload it always comes back with a 4238, no matter what version / build combination I put in. It's crazy, been at it for 2 hours now.

I'm wondering if there is any way certain build settings could make the uploader think there are 2 binaries?

I have a separate distribution profile for the main app and the extension, I also have 'Build Active Architectures Only' set to NO. That is all I can think of that would mess this up.

Any thoughts?

Answer 2

In my case I had to make build numer higher that last build number I uploaded. I had on iTunes Connect app with build number 3, then rewrote app from scratch and tried to upload new app with build number 1 I got same error, after changing to build number 4 it worked fine.

Answer 3

You need not to change the version number ,just change the Build number. But you should know that the Build number must be higher than last version you had uploaded. For example, your version number is 2.6.8 and Build number is 2.6.8 then you can change the Build number to 2.6.9. If you change the Build number to 2.6.8.0 it will occur a error say that the Build number(2.6.8.0) must be higher than the exist one(2.6.8) . So the key point is Build number.

@Jayprakash Dubey @Tenaciousd93

Answer 4

My issue was that the build number that I was updating in the General tab of Xcode wasn't changing the bundle version in the app's plist - so the uploader thought I was uploading the same build every time no matter what build number I was using. Once I changed the bundle version in the plist, everything worked fine.

Answer 5

I experienced this also, just increase the build number fixed it for me. I changed the build version to 1.0.1 and it worked. This can be found in the 'General' Tab in Xcode. Make sure you archive and validate again before submitting to App Store.

Answer 6

Tried many different build numbers myself. The only option that worked for me was to give a 4 figures build number : 1.1.0.1 (1.1 being my app version number on iTunes Connect).

Hope it helps!