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.
I am trying to upload a new build to iTunesConnect from xCode, but every time I encounter this issue:
What is the problem? and how can I fix this?
Recently I started facing issues during upload progress and Xcode used to get stuck a lot and would eventually fail with the second error which you are seeing. Having fed up for a while, I switched to use Application Loader in XCode.
Way to use would be, first archive your app, once that is finished, you can spot Export option on the right hand side panel just below Upload to App Store option. After you select Export You will see different options. Select Save for iOS App Deployment. This will create a .ipa file and save it in your desired location.
Now, go to XCode -> Developer Tools -> Application Loader -> Deliver Your App -> Select the .ipa file where you had saved before.
This method has been helping me a lot and failed not even once for quite sometime. Hope it helps you as well.
This happens due to Apple server is not working correctly for now, try to upload it later or 1 day after, it will be uploaded successfully, it happens due to Apple's app server internal problem.
Also you can try to upload it through App Loader. but if apple's server is in trouble then uploaded binary may not shown in iTunesconnect.
It would only work if I used Application Loader, like this:
First, export the application Archive from Xcode's Organizer window (it saves this into a directory on the Desktop).
Then, from Xcode:
Xcode > Open Developer Tool > Application Loader
My Xcode Version 8.2.1
I submitted my iOS app to iTunes Connect on yesterday but, the status is still showing “Processing” under Prerelease tab.
I found one link My prerelease app has been "processing" for over a week in iTunes Connect, what gives?
So, I changed the build version today and again uploaded .Today's Build is missing on iTunes Connect
Is this normal or is it a bug or I did something wrong? What’s my next option?
Thanks
It will take time to show your build on itunes connect. Some points you should cross check once before uploading again :-
1) If you are uploading build via Application Loader then check you version first. And I suggest you to upload it via xcode. Sometimes it happens binary get corrupt in "Payload" folder because there is some hidden files for eg .git or else. You should also check your Payload spelling for folder (Mistyping happens sometimes)
2) Check your email first , did you get any email from Apple. Sometimes it happens that our binary is not correct and further validation checked after binary upload. It shows in build section but after a while it is removed from there. You'll get mail regarding this.
3) Your build version should be greater then you uploaded previously.
Yes It is normal. Me too faced the same issue. So i upload the new build with different build number and it processing completed old and new build also.
The Reason behind it is the privacy issue in plist,
if u are using any UIImagePicker or any extra component so u must have to add key to plist.
Here is the some points to taken care.
1> Check all permission like location,photos,bluetooth if extra so remove it.
2> Add this if u using UIImagePicker NSPhotoLibraryUsageDescription
Photo Library Access Warning
I take about 1 month trying to upload my application but all to no avail. I called Apple, I followed the steps in your emails asking me to solve the problem but nothing works. I have tried everything, up from XCODE Version 7.1 (7B91b) and also from Application Loader 3.0 but again, nothing works, within seconds you have uploaded my application I get this:
In the image out compilations I uploaded to iTunes Connect, all with an exclamation point in red and says "There was an error importing the compilation"
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...