New build disappears after upload to iTunes Connect

Question

I am trying to load an assembly into iTunesConnect using Xcode 8. Xcode shows me that the download was successful. On the Activities tab of iTunesConnect, I see that my assembly appears, and it is marked as "processing ...". But in a few minutes this assembly will disappear, and I can not find it anywhere. I tried downloading it again using Xcode 8, but it says the assembly is already loaded into iTunesConnect. Therefore, when I tried to download the assembly with the larger version, it says “OK”, but I still do not see the assembly in iTunesConnect. I tried downloading using Application Loader, but there is the same problem.

Answer 1

Check your email. Overview The App Store may send you an email for use by the user.
It might help you. NSPhotoLibraryUsageDescription in Xcode8

Answer 2

You need to wait about 5-20 minutes, and you will find the application on the "Activity" tab (left).

If you are in the administrator position for this developer account, you will receive an email about the status of the assembly you created.

Answer 3

I also faced the same problem. After adding missing untouchable key data in Info.plist applications, the problem is fixed.

• Check and add the missing keys to the Info.plist file. For more information, see Link https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html .

• Some keys may be used by third-party modules included in your application. Find them and include them in your Info.plist file. (You can easily get them from the email in the App Store sent to you).

3. The following are the keys that fixed my problem, added NSBluetoothPeripheralUsageDescription, NSCalendarsUsageDescription, NSContactsUsageDescription, NSLocationWhenInUseUsageDescription, NSPhotoLibraryUsageDescription.

Answer 4

There was the same problem. Without access to the email address of this iTunes Connect account, it is almost impossible to detect that something is wrong (it seems that applications no longer fail if there are no privacy keys, as described here ). I think you know what features your device uses. Thus, you can try to add the secret keys that you need to Info.plist (check the "Privacy -... Description of Use" keys in the documentation )

Answer 5

There was the same problem. The assembly went away after a few minutes. No email, no errors ...

Finally, I added a second user to my account with a different Apple ID. This user could then receive an email explaining that some privacy settings (using Bluetooth) were missing ...

Apple, I just hate you as a developer. Bad tools, poor architecture, poor support.

Answer 6

I had the same issue and sent an email to the app store developer support. They answered me today as follows:

It may take up to 24 hours to process a newly created assembly. If your recently presented assembly takes more than 24 hours to process, we recommend sending a new assembly with a higher assembly number as this usually solves the problem. If after sending a new assembly you have a processing time of more than 24 hours, please reply to this message with the following information: - Application name - Apple ID application version - preliminary version and assembly number, which is currently being processed - a screenshot illustrating the current assembly (s) under TestFlight in iTunes Connect.

Give it a try!

* update:

I solve the problem after adding a usage description (e.g. photo, camera ...) to plist. *

Answer 7

I was able to send the assembly to the app store after adding all the privacy keys needed to be added to info.plist. Be sure to follow the link below the link to check the services that we access in our application that require privacy keys to support ios10 https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/ Articles / CocoaKeys.html

I missed the NSLocationWhenInUseUsageDescription secret key in info.plist, and after adding this key to info.plist I was able to successfully upload to itunesconnect.

Answer 8

With the Apple Support Staff, I found another reason that might cause this problem.

If there are earlier versions of third-party frameworks (in my case, GoogleMobileAds.framework was the culprit), the application assembly will be deleted after processing without errors or warnings. If you encounter this problem, check and update all third-party frameworks that are used in your application.

Answer 9

Hit the same problem. Tried all possible steps, including; 1. Increasing the build number 2. Adding the required usage description 3. Tried both options: Xcode8, as well as the application loader. Nothing worked in my case. The string has been successfully validated and shown on the itunesconnect Activity tab, displayed as Processing. as soon as you update the itunesconnect portal, it has disappeared.

Now, what happened: when the assembly is displayed as “Processing” on the itunesconnect portal, just wait and do nothing on the itunesconnect portal. DO NOT update the all builds tab for about 2-3 hours depending on your application size. (There seems to be no logic, but it was.)

After that, the binary will be available for sending to itunesconnect.

Answer 10

It happened to me also last week. With my old application, nothing has changed, I just want to release a new version with minor changes. I uploaded my IPA to the server, after some processing, the assembly disappeared from the Activity page. I also did not receive an email from Apple describing the error.

I opened an Apple ticket on Friday. On Tuesday, all my builds unexpectedly finished processing and became available on the Actions page. I think the launch was made by Apple. Then I sent my last build for review, and they answered my ticket, saying that since my build was in the queue for checking, is there anything else that they can help.

Maybe someone else can use this information and hope that Apple will update their system so that we can see the errors on the web page, if any, and not wait by email.

Answer 11

The assembly has disappeared. I wonder why, but did nothing. 12 hours later it was reported that it completed the processing, and I was able to deploy it for TestFlight testers.

Perhaps this is due to the fact that I accidentally downloaded the archive of my previous .ipa first through the Application Loader, and not from a recently exported one. But these may be random circumstances. In any case, I did nothing, and he appeared again, although after 12 hours, when the processing often ended in about 20-30 minutes.

Answer 12

I ran into the same issue, but this was due to a resolution issue.

The application requires permission to record sound, which was not in info.plist. Please check your info.plist and all necessary permissions.

After that, the application will be successfully sent and displayed on iTuneConnets.

Answer 13

I am facing the same problem. Application successfully submitted to TestFlight 4 days ago . But the tester said that she cannot see the latest released application in the TestFlight application.

I go into iTunesConnect and verify that the latest application was ready 4 days ago. But my TestFlight application does not see it. I update the list of applications in TestFlight 2-3 times and reinstall the application from TestFlight. Then the tester said that she received an email notification that the latest application is ready ... And I finally see the newest application.

I do not know what will happen in the end.

Answer 14

I am facing the same problem. I tried with various assemblies, but it failed, finally I checked my plist it has a permission key, but without a description. I used the address book platform to retrieve contacts, but later switched to CNContact, Key in plist worked fine without a description, but after adding the CNContact application, after loading it is removed from the Activity view in itunes.

Check if each permission key has a description or not, Apple can remove your application from Activity / Testflight at startup.

Answer 15

In my case, the problem was the lack of a BitCode flag. I don’t remember why I turned off the bit code, but I successfully download it with the bit code disabled for a month or so.

Suddenly loaded assemblies began to disappear shortly after the start of processing, but when I turned on the bit code, the download was correctly recognized again in the appstoreconnect console.

Now I finally receive emails with completed processing and can access the downloaded assembly in normal mode.

EDIT: A download without a bit code eventually appeared after 4 days, while a download with a bit code took 30 minutes.