New build disappears after uploading it to iTunes Connect

Question

I\'m trying to upload a build to iTunesConnect with Xcode 8. Xcode shows me that the uploading is successful. In Activity tab of iTunesConnect I see that my build is appears and

Answer 1

Got hit with same issue. Tried every possible steps including; 1. Incrementing build number 2. Adding required usage description 3. Tried both options: Xcode8 as well as application loader. Nothing worked in my case. Build was successfully validated and showing in "Activity" tab of itunesconnect showing as "Processing". once you refresh the itunesconnect portal, it got disappeared.

Now, what worked is : Once build shows as "Processing" in itunesconnect portal,just wait and do nothing in itunesconnect portal. DON'T refresh the all builds tab around 2-3 hours depending on your app size.(Seems no logic but this is the way it worked.)

After then, binary will be available for submitting in itunesconnect.

Answer 2

I encounter the same problem. The app did send to TestFlight successfully 4 days ago. But tester said, she can not see the newest released app in TestFlight app.

I log in iTunesConnect and verify the newest app have been ready 4 days ago. But my TestFlight app cannot see it. I refresh app list in TestFlight 2 ~ 3 times, and re-install app from TestFlight. Then the tester said she receive the notification email about newest app is ready.... And I can see the newest app finally.

I don't know what happen at the end.

Answer 3

With the help of Apple Support Staff, I found one more reason that can cause this problem.

If there are older versions of third party frameworks (in my case the culprit was GoogleMobileAds.framework), the app build will be removed after processing, without errors or warnings. If you encounter this problem, check and update all third party frameworks that are used i your app.

Answer 4

Had the same issue. Without access to email of that Itunes Connect account, it's almost impossible to detect that something is wrong (it seems, that apps not crashing anymore if privacy keys are missing, as it described here). I guess you know what device capabilities your app uses. So you can try to add privacy keys you needed to Info.plist (check "Privacy - ... Usage Description" keys in the docs)

Answer 5

In my case, the issue was that I had started preparing the release while the archive was being created.

I had uploaded v1.0.0 of my app, and it had passed app store review and was available for sale.

Based on user feedback, I made some very minor changes to the UI text ONLY and created v1.0.1. No changes to libraries, no new permissions etc. Imagine my surprise when I was not able to see the build after uploading.

I ended up resubmitting 5 times (build 7 to build 11). I even downgraded my version of xcode and retried. Nothing helped.

Then, I remembered that I had started creating a new release v1.0.1 in the App Store and had saved the new release information. My thought was that once the build was available, I would attach it and submit for review.

I could not find a way to delete the partially created release, so I changed the version in xcode to v1.0.2 and retried. And it worked.

I then changed the app store release version also to v1.0.2, associated the build and submitted for review.

Screenshots of the lost releases:

Answer 6

Check your email. App Store review may send you a email for User Usage.
This may help you. NSPhotoLibraryUsageDescription in Xcode8