App submission issue with new iTunes Connect

This seems to be a frequent issue but here is someone who solved his particular problem---I don't think the answer is the same for everyone because we all use different features in our apps so a lot of things have to be validated---

DinucleusSep 10, 2014 3:28 AM Re: Can't submit for review after got Metadata Rejected in new iTunesconnect
Re: Can't submit for review after got Metadata Rejected in new iTunesconnectin response to jacks8x

I tried the following and it seems to work:

1. After I got the Metadata - rejected I didn't see any builds available -> but there was no error that I was missing a build. Moreover, the message from Apple was saying that I didn't had to upload a new build.

2. I uploaded a new build from xcode, with out a problem - even if my app was not in waiting for upload state.

3. I chose the build -> which I could not do before

4. Pressed save

5. Pressed Submit for review

And now my app is in Waiting for Review state...not sure how long it will take for Apple to Review it...(I will post an update when there is a change!)

We all get at least one instance of technical support with our license---if you can't solve this maybe this is the time to use that.

My metadata was rejected before they changed the system. So I didn't have any builds as usual, and the rejected metadata was for a new app, so there are no previous versions.

My best guess is that unofficially Apple is expecting us to provide 4.7" and 5.5" screenshots before we can proceed. From what we see they don't look required, but when it comes to submitting it may cause problems as the one I am having.

You can't hit "submit for review" without saving any new data

I am having the same exact issue. I have contacted Apple through the Contact Us form (last night) haven't heard anything back yet. No matter how many times I go through the Submit for review process is just dumps me back on the app page and still says "prepare for submission".

I had the same issue. Mine was fixed after I rejected my Build then ADDED 4.7 and 5.5 Screen Shots.

I was then able to select my uploaded latest build, save, etc.. and submit..

i.e. MUST get the New Screenshot sizes!

I dont see a "+" nor a delete icon anywhere in the build section under versions nor pre-release section. another *** moment.

Unfortunately the explanation of how the new process works is not the best, and the screen flow is completely different and not exactly intuitive.

The process does work though. Here are the steps you will now go through:

1. Create a new version on the iTunes Connect Website
2. Make necessary changes to version info, and be sure to edit the Ratings info because there are a couple of new ratings items. and press Save.
3. Create your build in XCode and Upload to iTunes Connect as you have done in the past. Note that there are new screens in Xcode 6, but the process is pretty much the same.
4. Now the difference: Your upload goes into a new area called "Pre-Release". Your App now goes through a new review step. This has taken for me from 5 minutes to two hours. I don't know what the service level is for this step.
5. Once the Pre-Release review is complete, your uploaded App will become available for "Official Submission", and the "+" will now appear on the Versions screen.
6. Click the "+" sign and you will be prompted to select a build.
7. Select and build and press Save at the top.
8. Finally, click on Submit.

Hope this helps. I've done a few submissions now, but that 1st one is painful. You may want to explore in here, there are are few good things and quirky this that it appears Apple is working through. One thing you may want to try is the new integration of TestFlight into iTunes Connect.

I think we just need to be a bit patient with these significant changes.

Steve S.

my app has been sitting in prerelease for over 24 hours now

This is insane... is there ANY reason why I would have to wait over 2 hours for the binary that I successfully uploaded from the Xcode Organizer to appear in ITC? In all honesty, it did not appear, and while I was waiting I made a few changes, but the only way to submit the new version was to increment the version number.

So now, I am, once again, waiting to see if my binary will show up after successfully uploading from Organizer.

Why, Apple, did you not only make an horrible UX for submitting apps worse, but also break one of the only things that worked half-decently (the uploading and rejecting of binaries)????

Please fix this, please, oh please, oh please...

What is happening?

The Submit button is not highlighted even though I have ticked all the boxes.

I even tried different combination of the radio boxes.

Since the new xCode and iTunes Connect there are so many bugs, it's time consuming to get an app up there.

I have the exact same issue. Submit button can't be clicked.

Glad it's not just me. I thought I was loosing my mind.

It works now. There's a new section regarding encryption. After answering the questions, the submit button is clickable.

DailyLook_Dev,

Take a look at my post on Sept 23rd. I have documented the publication steps. Also You didn't need to generate a new Version, but just a new Build. We update our build number anytime we publish to TestFlight or AppStore. This is very helpful for help desk support. Version and Build can be displayed under iPhones settings, so your Help Desk can ask the user for this information. The convention we use in all our Apps on all platforms (Windows, Android, Apple, LINUX, etc) is YYMM.nn example: 1410.02 this way we know immediately the age of the build as well as the occurrence within the month. Apple has a recommended standard, but they don't realize that some shops have had standards in place for years, and thinks its arrogant of them to expect us to change to their convention for no value-added reason.

I went through what you went through, and I was ready to scream several times. I had an App to move in and it was 2 days after the new site went live, so I maxed out my frustration level. The root cause is that Apple provided no introductory information to walk us through the change and I think they thought the site was intuitive... Obviously not! I have other issues with the current site though: 1. The site may alter a build number when you have leading zeros. Ex: in XCode 1409.03 becomes 1409.3 on the site. Why? and 2. You can't delete Pre-Release versions, so I now have old "bad" versions i don't need sitting there.

Anyway, I think in the long run the site will be better and offer new capabilities such as: 1) Being able to deploy previous releases. 2) Integrated Beta Testing with TestFlight.