ITunes Connect: Cannot save application information after downloading a new binary

I am trying to download an iOS application to view using Xcode Organizer, and I ran into two problems:

Case 1

Downloading binaries, but when I click Submit to View, iTunes Connect reports an error:

Information about your application cannot be saved. Try again. If the problem persists, contact us.

Case 2

After receiving the first error message, I tried to download a new binary, but received the following error message in Organizer:

ERROR ITMS-9000: "Backup binary download. Binary download with assembly version '1.1' for train '1.1'"




I tried to load other binaries by changing the version number, but still I can not get my application to go into view state. I also see no way to delete old downloaded files.

Another observation: My application should be about 30 MB, but when I look at the downloaded binary, it is only 1.46 MB. I suppose there might be something wrong from the binary, but I have built it several times using the same technique and have never had any problems.

Any ideas?

+46
ios xcode itunesconnect
Sep 06 '14 at 6:18
source share
26 answers

For me, I filled out a form in Safari and got an error. I logged out, then switched to Chrome and signed up. This fixed the error and I was able to submit.

+62
Sep 09 '14 at 23:23
source share

Exit and entry should work again, as it worked for me!

+18
Nov 04 '14 at 4:36
source share

I solved this by increasing the number in Build (select Target, then Xcode โ†’ General โ†’ Build, see the figure), adding .1 so that the build was 3.75 โ†’ 3.75.1 . But only for assembly, the version is still 3.75 , and also appears in iTunesConnect.

Showing where to set the Build Version in Xcode

Then a new binary was loaded, and I could select it for viewing. In the image below, you can see the old and new binaries listed in iTunesConnect. Then, finally, I just had to select a new binary file and submit it for review. Showing list of binaries in iTunesConnect

+9
Sep 06 '14 at 11:17
source share

Open the web inspector, you will find that Apple said: We've got a server error ... 500 This is the real reason. :)

Update:

Inspired by @phantom, I am trying to use dotjs to run a javascript script to automatically click the submit button in 15 seconds, but still get 500 errors all the time.

@ Answer Geaka works for me. Since my product name is Chinese, I change my product name to English (DO NOT include spaces! Perhaps this causes a different error when creating a path error.)

I am debugging an apple website and find a js script called submit_for_review_cntrl.js that monitors all the sending progress. From line 123 to line 129 (formatted with the {} button in chrome), which sets the http headers, there is a field called X-Original-Filename , the value is set by the $scope.addCcatFileToJson method on line 138, the parameter of this method is set by the ajax callback, I assume that there is an error for coding the product name field of the internal code.

+8
Sep 06 '14 at 13:37
source share

WTF Apple!

We just solved our version of the problem (general error message) ...

After I got into submit for viewing, I tried to upload the file for ERN, since my application uses encryption. It finally worked when I used a zip file containing an ERN response image and a txt file describing which encryption is used.

+6
Sep 08 '14 at 2:06
source share

The problem, unfortunately, is still happening. My solution, when this happens, is to delete the binary, click the save button, and then add the binary. Then save and follow the standard procedure. This solves the problem for me without changing the version of the assembly or nothing more.

+6
Mar 15 '15 at 8:02
source share

Finally, we find a solution:

Steps:

  • If your application version and assembly version 1.0, save version 1.0 and change the assembly version to 1.1 (more than the latest version of the assembly), and then download it. If your application name is English, select this assembly and submit it for review, this will be a change for review.

  • If your application name is not English , for example, in Chinese, you should name it in the Display name of the package , Do not name it directly in TARGETS .

Perhaps also works for Japanese and Koreans.

+3
Sep 07 '14 at 1:35
source share

I solved this by switching to Chrome instead of using Safari. Presto, worked right away!

+3
Sep 22 '14 at 22:10
source share

I met this problem this morning and solved it. I change my product name from Chinese to English and write the Chinese name in the Bundle display name that solves this problem. You can change the Bundle display name in the info.plist file and change the product name on the General tab in the project.

+2
Sep 08 '14 at 5:25
source share

which is a mistake. Perhaps some problems with Apple's infrastructure. Perhaps you did something, and then it worked - switching your browser, increasing the number of build numbers, etc. But you could hit several times. At least after a while, my performance was successful.

+2
Sep 23 '14 at 6:45
source share

I opened an iTunes connection on my iPhone and was able to successfully submit via iOS Safari. I do not know why.

+2
09 Oct '14 at 21:15
source share

I need to clear all my cookies, not switch the browser.

+2
Jul 03 '15 at 7:56
source share

You will need to change the build version. Create a 1.2 build for version 1.1 of your application. Then upload your binary file. After a few minutes (during processing) you will find a new assembly for presentation to view.

I spent 2 hours !!!

+1
Sep 06 '14 at 8:37
source share

Finally, I found a solution. The main culprits are your PRODUCT NAME, it must be in English!

  • Go to build settings โ†’ packaging โ†’ change your product name to English
  • Change your "display name BUndle" to your localized wish name
  • Increase your build version and reload

This time everything is in order !!!

+1
Sep 08 '14 at 6:35
source share

I came across these errors again and again when adding new screenshots. Nothing seemed to help.

Then I visited iTunes connect in Safari (I usually use Chrome) and somehow all the errors went away. Maybe due to the extension of the Chrome browser, for example AdBlock?

TL; DR; use Safari for iTunes Connect

+1
Sep 08 '14 at 10:12
source share

I experienced this by submitting an update for my application. For about 30 minutes I repeated and got the same error. I tried removing the binary, exiting it, I also rebuilt the binary with the added โ€œBundle Version Stringโ€.

None of these steps mattered, but I kept trying again, kept getting the same error, and in the end he agreed with the view.

I do not believe that any of these solutions that I tried had any meaning. I believe that inside itunesconnect there was an internal error. As the message suggests, I think all you have to do is try again later ...

+1
Apr 15 '15 at 11:07
source share

Switch the browser you are using and then delete the assembly, save it once, then add the assembly to it again and then save it. After that, click on submit to view, and it will work perfectly.

+1
Nov 19 '15 at 15:36
source share

After 3 days, iTunes accepts my first binary. I tried changing my Bundle display name to English, and then tried changing version 1.0 and changing versionon version to 1.2. I also tried to think a lot after a 3-day surprise !!! Apple accepts

0
Sep 09 '14 at 9:21
source share

I also got this error. The solution I found was to change the contents of the "Name" section in the application description in iTunes Connect.

There was no need to change the application name to English (as some suggest), I just deleted the ":" character from the application name - and then I can send it for review! My localized versions of applications still contain non-English names.

0
Sep 09 '14 at 13:07
source share

Had the same problem as my application name contains ":". Because of this, the iTunes connection server returns 500 errors. I just temporarily deleted ":" from the English name of the application, sent the application, and returned ":" back.

0
Sep 09 '14 at 13:33
source share

I think this turned out to be a combination of several factors, but one thing that was definitely wrong was that I did not click on the box with information about placing information in a Korean store. This was disabled by default and needed to be clicked. After this and several version changes (in the end, I introduced 1.2 instead of 1.0!) My application finally switched to "waiting for review ...".

0
Oct 02 '14 at 3:43
source share

Tried all possible solutions of Chrome and Safari; none of them worked.

Then I switched to Firefox and went through the magic.

0
May 21 '15 at 2:15
source share

I found a simple solution. Just go to the version details, delete the current assembly, then save.

Then click the blue add button and add the current assembly again, save again. Then send again.

This works for my business. Hope this helps.

0
May 25 '15 at 4:39
source share

Exit iTunes from the current browser. and sign in to iTunes from another browser and try sending the app.

Hope it works!

And make sure there shouldn't be a backup binary (in other words, the build number of the binary should not match).

0
Jul 02 '15 at 7:12
source share

I had the same problem.

Switching browsers in Chrome immediately fixed this for me, so try clearing Safari and rebooting to return to sending using Safari.

@rayg - and for others - the Korean flag does not need to be checked to succeed in getting the application to view. Perhaps, under certain circumstances, you need to select it, so I'm not saying that your decision in your scenario is incorrect, but the message created the impression that this is a requirement for each application presented, and this is not so.

0
Jul 02 '15 at 13:40
source share

I tried all the recommended solutions, but none of them worked for me. Then I select the build version from my mac system and burn itunes connect using firefox from the window system, and it worked for me. Or you can try itunes to connect to login from another Window / Mac system.

0
Aug 05 '15 at 10:39 on
source share



All Articles