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?
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):
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.
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
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.
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
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.
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 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?
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 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:
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!
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.
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.)
Related
I made a new build of my app (version 2.2 build 11) and uploaded to App Store Connect.
Then I used "(+) Version or platform" to prepare version 2.2 for submission. When I press "Submit for Review", I get a warning:
Newer Build Available
Are you sure you want to submit this build for review? A newer build of your app is available. To submit the newer build, delete this earlier build and resubmit.
The currently released version of the app is 2.1. The "Activity" tab of App Store Connect only shows this build (11) for version 2.2. Build 10 was version 2.1.
What does this error actually mean, and how am I meant to resolve it? The obvious thing is to try deleting this build and resubmitting it, but I'd like to understand more about the error, especially if it turns out deleting and resubmitting doesn't help (haven't tried yet).
Solved it.
As an infrequent iOS developer, I thought that specifying the version number after hitting "(+) Version or platform" would be enough. But I missed actually choosing the build far down in the submission form.
Presumably it defaults to the previously submitted build, which in this case would be 2.1 build 10, causing the error.
So the error message could have been better, but it was ultimately something I missed.
Check Activity tab, if it says 'Processing` than you will not be able to add the build to the release, and you will get this error message.
Wait for about 10, minutes for it to complete, add your build to the release, and you are good to go.
I have successfully uploaded my iOS build on App Store today. Its been more then 5 hours now and the build is still not shown in Activities. I am using Xcode 10.1 to upload build and uploaded build using Xcode update build option. What needs to be done. I have tried to upload the same build again, but got "Redundant binary upload" error.
I had a similar issue. I upload a version with build number 2 and it was totally disappeared, I didn't find it anywhere and I can not re-upload it. I upload another build with number 3.
My app was approved and everything is okay. Today I received an email from Apple which said that I already have a build with a bigger version and I have to upload a new build bigger than 3.
I think somehow the service just hanged for a while(at least 2 days). But it hangs only the specific upload of build and it is not affecting the app.
You have several options:
Just wait
Create a new build with a bigger build number
Create a new version.
I did the second option and it was okay
Change the version of the app for example if it was 1.0 -> change it to 1.0.1 or 1.1
But you don't have to change the build if the app is not published to the App Store yet. Also make sure the build has been changed inside the .plist, that happens sometimes.
when you upload through Xcode to iTunesConnect it's can take a lot of time to process your build so just wait and it'll be finished eventually.
I have developed app and so many times I have uploaded on iTunes connect (TestFlight). Like :
Version Build
1.5 —> 1.0 This build is live — on App Store
1.4 —> 1.9
1.4 —> 1.8
1.4 —> 1.7
1.4 —> 1.6
……….
1.3 —> 1.9
1.3 —> 1.8
……..
and so on…..
Now I need to update one change and want to give for testing to my other friends, So I am trying to upload new version `1.5 —> 1.1’ on iTunes connect (TestFlight) through Xcode, but it gives error like : Version must be higher than the existing version on iTunes connect.
Before making live, I have uploaded so many build for the same version and same via Xcode , at that time it is done successfully uploaded.
Then why it gives me error now ?
What it means to say ?
How can I upload on TestFlight for testing ?
Please suggested me, what should I do.
It could be due to your app has become Live (Ready For Sale) on the AppStore.
I think Apple consider the version life cycle completed once the version is available to public users via AppStore.
In your case, 1.5 (1) is Live on AppStore which means version 1.5 life cycle completes with final version being 1.5 (1).
So, you would not be able to add any further new build with 1.5 version. Instead, you should create a new version higher than 1.5, i.e., 1.5.1, 1.6, and then upload the builds to that newly created version.
This is just my assumption, not 100% sure.
For me.. i regularly updating build(not version) and uploading the it to testflight and works, even i have uploaded it today just 1 hour ago and it worked fine. I think, you should clean->build and do same process again. Sometimes after changing build number, you might not have build the target and directly archived, in that case, such a errors are thrown by Apple.
So the probable solution is to just
clean->build -> archieve .... do same process again and upload it to appstore.
I had the same Issue. I released 1.0 build 5 to App Store(live). Had to make some quick changes, so tried to change the build number and released to Test Flight through iTunes Connect. I got no warnings or any errors. However, when I login to iTunesConnect and check in Activity tab the build number for that specific version says "The build is invalid" with a red exclamation.
Solution: Just increase the version no, not the build no if the app is already live.
I'm getting error "Redundant Binary Upload. There already a binary upload with build version'1' for train '1.1.2" at Softwareassets" when trying upload an updated version to appStore.
However, I already incremented "build" version number. as shown below:
Moreover, I notice, one issue, even though I changed build and version numbers, but still Xcode display the old version number when display the error and also in the details under organizer windows:
Notice, actually my app version and build numbers are 1.2 and 1.2.1 respectively on General settings.
I dont know why xcode doesn't realize that version and build numbers have changed.
I am not sure that this will help, becoz even I had faced many unpredicted issues while submitting the apps recently.
But for the basics,
if app is not reviewed yet:
Your Version number must be same as It is there in itunesConnect Account,
and you can update the new build with updating only build number
And if your is reviewed or published:
you need to update both version and build numbers
Also, if possible once try to submit the build from xcode and submit the app from itunesConnect.
Hope this will help,
Thanks.
It seems I asked the wrong question. I'm getting this error because I forgot to archive the project first before uploading to Appstore.
The reason I didn't archive because archive was giving an error which I posted as as another question at stackoverflow.
I had submitted an version 2.0 of my app for review recently.
It got rejected by apple for a valid reason.
I made the changes and tried to upload a new binary with the same version say 2.0
But it wont upload it via Xcode saying an binary with version 2.0 already exists.
I couldn't find any way to remove the 2.0 rejected build from the Pre-Release tab.
I tried this
reject this binary in new itunes connect UI .
But this did not help either
Thanks in advance.
Cheers.
You don't need to increase the version number. But increasing the build number should allow you to submit.
Note that this is in the "new" iTunes Connect. The idea being that you can have multiple versions being tested by different groups of people. The unused builds are removed when they expire (note that there's a date attached).
Try increasing the version number and build number then submit the binary