I tried to publish the app to Apple Store Connect. Normally there is a "+" button but I don't see one right now because Apple have updated iTunes Connect and introduced a bug. How can I get around this bug and select a build to submit my app to the App Store.
I cannot choose the build to Submit for review.
I just uploaded a new version a few days ago, and everything seems to be working just fine on iTunes Connect. Could you please make sure you're following the steps below:
First create a build from Xcode with a specific version number (for instance 1.3.0), archive and upload to iTunes Connect. Wait a few minutes for the build to process.
Once the build has finished processing, make sure it's available on iTunes Connect by navigating to My Apps/Activity/iOS Builds. If everything is okay you should see your new build "Version 1.3.0" here.
Now before you can change the build, and this may be the step you're missing, you need to add a new version of your app for submission, via "+ Version or Platform". This number should match the build you uploaded earlier (1.3.0).
Then just select the newly created version of your app on the left menu, and you will have the option to select the new build you want to use for this version in the "Build" section.
I had the same problem. The Step 2 in #user13639548 answer confused me even more because I didn't find activity/ios builds.
What solved the problem however was changing the versin from 1.1 to 1.1.0. and then also waiting 3-5 more minutes until the + button appears again.
I archived a new version of application on XCode and uploaded it on app store using XCode , however when I open all builds from app store connect , I am not able to find the build. Thus I am not able to choose the build on the version. to submit for review.
I'm having the same issue as well, it has been 20 hours since I upload my build when I'm writing this and it's still nowhere to be seen.
I also tried to upload a second build and it's also not showing.
So I believe it's an Apple issue and not isolated, looks like we can only wait for now.
Edit: It works now. I assume it works for everyone now.
I also had this issue this morning. I have just now uploaded a new build of my app and the new build now appears, the missing one still doesn't appear. You will need to change the version number and re-archive your app, as otherwise it will be rejected as a redundant upload.
Update after 10 minutes the new build also disappears. Awesome..
After archieved file uploaded successfully it will go into processing stage. Where they are checking the internal settings using the automated tools.
Things will be checked like if any permission issues coming etc.
Lets say of example if you are using camera into your application but you have not given permission into.plist file than it will get failed into processing & removed build from the App Store.
Also if you have set up the permission properly but not given instructions that how & why this gets used than also build will get failed into processing stage. So there can be various reasons.
Ofcourse they will send you an email to your Admin email Id about the build failed while processing with the reason so by that you can resolve the issue.
Hope this will helps to everyone.
Recently I have noticed, that Apple's TestFlight app provides possibility to install older builds of application (application is during internal testing).
It is actually a nice feature, but is there any chance to remove some build that I don't want anybody to install anymore?
My case: I found some bug in app, that causes problems on a server-side - app simply overrides data. Problem in app is already solved in build X, but TestFlight still allow user to install build X-1.
I've tried:
found this option
stop & start testing
change app version (from 0.1 to 0.2) but builds of version 0.1 are still available - probably until expiration date (60 days from
upload)
Under TestFlight builds (ios),
If you have multiple builds, select the bad one.
Next expire the build, currently on the righthand side of the screen.
This does not solve the problem. The problem is that if you have "Manage Version and Build Number" checked in XCode Distribute App, it will create a new build number for you if you forgot to update it before you Archived. Consequently, builds can be uploaded to TestFlight and assigned a new number which you may not want - such as when XCode Distribute seems to have shown an error but actually has uploaded the build anyway.
In our case, we need to keep the build numbers in sync with our Android builds using Flutter. Yes, you can expire a build, but that build stays there and you can't delete it!!! Is there ANY way to actually DELETE the build, not merely expire it???
My connection was dropped while I am uploading the archive to the apps store.. and it showed Uploaded successfully with big green tick..
And also it goes to the app store and wait forever in the processing state. So I just uploaded it with the new build number and it's processed within less than 10 minutes.
but troubles are not over :(
then I couldn't select my latest build for test it still showed that stuck one..
What can I do for this ?
====================================================================
This has happened to me a few times already i.e. when a binary doesn't finish processing due to connection drop or other issues (on apple side).
Just upload a new build and use that build for release or test flight. Don't worry about the build that never finishes. Just ignore it and move on.
If you are still seeing build 2 as the latest under testfligth section, then logout, clear your browser cache, log back in and see. Clearly your build 3 is the latest one. itunesconnect is super flaky.
Use apple support as a last resort. They will take days to solve something as simple as this.
In my experience when the build stays greyed out and (processing) for longer than a few minutes it will stay forever like that. Best to just re-upload and wait for the new build to process. It does take a bit of time to show up for testing though.
These are the steps which I did to got build to the testflight internal testers
to show Export Compliance add below line
to info.plist
<key>ITSAppUsesNonExemptEncryption</key><false/>
change version no to different one (not the build no)
create archive and upload it without upload bitcode enable tick
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.)