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.
Related
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 know its duplicate question, I want to update my app and after getting upload successful through the Xcode I can't see the new version...
I want to know how long it usually takes until ill see that? and if after I got upload successful could be another problem why its not upload? if yes what are the problems might be?
I updated the version and the build number, so its not the issue
thank you for the help
So I will post an answer since a comment is to short to answer this.
So the step for the release are:
Upload a build from Xcode
Wait for the build to be processed (this can take some time)
You will be notified by itunesconnect when the processing is done
In this stage the processing can already detect some issues with your app, like missing assets or something like that
You can check the status of your build in the activity tab
You won't get any "App Store status" until you actually release it. Now after the processing is done, you can select the build from the "My App -> App Name" in the "Build" section, there is a "+" that, in my opinion is placed very bad.
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
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
This has been happening for multiple build recently for my account. I upload the build to TestFlight. It gives me a success message. However, it creates 2 entries for the same build even though I upload the build just once as seen in the screenshot below. One of the entries remains in Processing state forever. The other entry completes Processing and becomes Active.
After the entry is Active, if I go to the TestFlight option to select it for testing, it shows it grayed out and doesn't allow me to test this.
The only way I can fix this is to generate another build with a new build version string and upload it to TestFlight and hope that it doesn't get stuck the same way.
Anyone else facing this issue and any advise on how to fix this?
Thanks.