获得 ITMS-4238“冗余二进制上传”错误，无论我改变了构建版本或应用程序版本

我拒绝了一个二进制文件，它是1.0(1.0)。 这个状态被开发者拒绝了。

我去上传一个新的二进制文件，遇到了这个问题，然后我看到我需要增加我的构建。

我增加了应用程序版本和构建到1.1，这是一个错误。

我得到了一些错误的应用程序版本不匹配，理解。

然后我尝试了应用程序版本1.0和许多不同的构建编号。 1.1,1.0.1.1.2,1.3,1.0.3. . 没有工作。 我一直得到这个错误。在 itunes connect (1.0)上只列出了一个 build

我试过不用二进制，但上面说我需要一个。

我甚至尝试将应用程序版本改为1.1，在 iTunes 上连接，然后上传 1.1(1.0) ，这也失败了相同的重复问题。

有人遇到过这种问题吗？

Screenshot for error

53671 次浏览
小开
最佳答案

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.

小开

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):

小开

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!

小开

I guess, since Apple has integrated test flight into itunesconnect, there is a difference between version and Build (which is the wording they use in project-settings->target->generalScreen) and in info.plist its equivalent is "Bundle Version String short" and "Bundle Version". Here the wording has never made real sense to me.

I have gotten the error with version 2.2 and build 2.2. I changed it to version 2.2 and build 1 (because it was my first upload) and it worked.

小开

I tried ApplicationLoader 2.9.1, it's working for me. ApplicationLoader 2.9.1 can download from itunes connect.

小开

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?

小开

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

小开

I have uploaded the app, but for missing screenshots for 3.5", I got the same error. And could not upload again from xcode.

(So I make an ipa file, in xcode organizer and export as ipa). But when I press the upload build in the itunesconnect then it take the old uploaded file (give me an option to choose). And then after saving this, I got the option for submit for review.

(If you go to the pre release tab in itunesconnect, you can see the previously uploaded app.)

小开

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

小开

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.

小开

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.

小开

I solved same problem...I uploaded a version 1.01 and build 1.1 then I decided to reject this compilation. I Changed on i-tunes version to 1.1 and tried to upload new version 1.1 build 1.1 and I got error. Then I change on xcode to build 1.2 and upload ok.

小开

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.

小开

Check if you have used the run script: enter image description here

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!

小开

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

小开

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.


提交答案