Your app information could not be saved

Actually, on second thought, and after having used it more extensively, it's better than I thought.

But, after you submit a version for review, sometimes the 'Cancel submission' option is not always present. It should always be present if the developer

has submitted a version for review. It can be frustrating not being able to locate the cancel option.

Also, the app submission pages are *really* sluggish. There seems to be about a 1 second delay from the time I initiate scrolling of the page and having the page respond. As a comparison, when I scroll through my gmail emails, it's quick to respond, so I don't think it's my computer.

This sluggishness is *really* annoying. Is it making some kind of server side backend call(s) during the user initiated scrolling ? My guess is that there's some unnecessary processing that's taking place during user initiated scrolling, that shouldn't be taking place.

And, in fact, this sluggishness actually makes it more difficult to step through the submission pages. It feels like I'm trudging through molasses and because the scrolling is so sluggish, it makes it hard to ascertain that I've filled in all the fields on the page correctly.

I got the same message.

After reviewing some of the answers here and the comment from Apple (asking which browser you are using) - I tried it again with Safari.

Then I saw the real problem - my selection about the IDFA was not matching the binary - so i had to click Yes and provide the relevant details.

Then I was able to submit.

So if you think Apple's QA team is using other browsers - think again..

Or maybe they do, but if you think that Apple's developers are using other browsers - think again..

Yesterday I got the same message. I have tried some methods on the same browser but it did not work. This morning I have tried it from a different computer and luckily my problem is solved. I did not try it from the computer at home so I am not really sure about the cause of the problem. My guess is that it might be a problem regarding the web browser. So you can give a try to the following:

• close all tabs and the browser itself and restart it
• use a different web browser
• wait for some time and try the previous ones again

hope it works.

It seems to be much better now than it was a couple weeks ago.

I haven't seen/noticed any sluggishness lately. Also, after you upload the upload, give the iTunes Connect site 5-10 minutes for it to process the app.

If the uploaded app status is 'Uploaded', that means it hasn't processed the app yet, so you won't be able to associate the binary with your release

yet.

The entire workflow feels a lot smoother now. I think part of it was just getting used to the new way of doing things.

But also, I think Apple tested all the individual components of the workflow separately, but never tested the integration of the various components until after it had gone live with the latest workflow changes. I suspect this because when I was using it a couple weeks, the individual components seemed to work fine, but all the pieces didn't work well together. e.g. the upload to iTunes would indicate that it failed, when it actually had succeeded. The IDFA (Identifier for Advertising) handling was clumsily integrated (the iTunes upload would show as failed if you were using the IDFA in your app, even though it hadn't failed). Also, it wasn't clear that you had to wait for the uploaded binary to change in status from 'Uploaded' to something else before you could access it.

Most of this I think could have been better handled by doing some integration testing. Testing uploads/submission process for apps with IDFA's should have been done prior to production release -- apps with IDFA's (ad supported apps) are probably the most common type of apps submitted to the Apple App Store. Again, it didn't look to me like anyone had ever integration tested this case prior to the latest system going live, because it worked so poorly a couple weeks ago.

Anyways, things look pretty smooth now and I am already forgetting the extra hours of frustration I expended a few weeks ago. 🙂.

I have same problem

This sounds crazy. But if you get this error login in to iTunesConnect from another computer or device like your iPhone and submit. It frustratingly works.

Works for me:

close all tabs and the browser itself and restart it

I had to wait for 24h. Then I could submit the app again.

Got the same problem too...really frustrating.

I switched between chrome and safari for several times,

and then resave it after removing the binary and then ... add the same binary, save it, and finally it's done.

Maybe just repeat saving it every 5 seconds can solve it.

I had the same problem.

I could resolve it with removing and adding the application-build again in itunesconnect. After saving everything I could submit it for review successfully! :-)

Greetings, please follow the below steps:

Go to my Apps page, remove the build, save it and re add your build, save it and try to submit.

Best regards

I tried this... getting the same problem...

Issue was solved. Quicktime records at 48fps which is the wrong frame rate.
Using something like Final Cut Pro X or Adobe Premiere allowed me to change the rate to the required 30fps.

Why doesn't QuickTime offer this functionality? It would make it all a lot easier and save Apple from being bombarded with support requests.

This worked for me; thanks!

Follow the below steps.

1. Go to My Apps Page.
2. Remove the Build. Then Save It.
3. Re Add your Build. then Save It.
4. Now try to Submit It must work.

This worked for me, thanks!