Submitting the App

After you provide app configuration information, as described in “Creating an iTunes Connect Record for an App,” you’re ready to validate your app information and to upload your app binary.

Make sure to configure and validate the following properties that cannot be changed after you submit the app:

Make sure to validate the following properties that will cause your app to be rejected if the iTunes Connect information doesn’t match what’s set in the app binary:

If you’re uploading a new version of an existing app, see “Replacing Your App with a New Version” instead of reading this chapter.

Reviewing Your Version Summary

The Version Summary page is a read-only summary of all the metadata and assets you’re about to submit to Apple. Remember that even though you can edit your metadata after you submit the app, not all metadata properties can be changed. To learn which properties are editable and when, see “Version-Level Properties.”

Use the Version Summary page to review the metadata for each store territory.

bullet
To open the version summary for an app
  1. Open the App Summary page for the app, as described in “To open the App Summary page for an app.”

  2. In the Versions section, click View Details for the current version.

  3. Click Version Summary.

    ../Art/apps_version_summary_2x.png../Art/apps_version_summary_2x.png
  4. Review the app information as it would appear in the store for a given territory.

    Choose a territory from the Territory menu.

    ../Art/apps_vsummary_territory_2x.png

For additional ways to validate your app metadata, see “Viewing App Information” and “Working with Catalog Reports.”

Uploading Your Binary

When you’re ready to upload the app binary, iTunes Connect steps you through final questions before setting the iTunes Connect record to Waiting For Upload. When a record has this status, Xcode and Application Loader can access the metadata for the app so you can associate the binary with the iTunes Connect record.

bullet
To begin the Ready to Upload Binary flow
  1. Make sure that you have completed all the configuration the app needs.

  2. For iOS apps, check that your app size fits within the App Store requirements.

    iOS App binary files can be as large as 2 GB, but the executable file (app_name.app/app_name) cannot exceed 60 MB. However, consider download times when determining your app’s size. Minimize the file’s size as much as possible, keeping in mind that there is a 100 MB limit for over-the-air downloads. Abnormally large binary files are usually the result of storing data, such as images, inside the compiled binary itself, instead of as a resource inside your app bundle. If you are compiling an image or large dataset into your binary, it would be best to split this data out into a resource that is loaded dynamically by your app.

  3. Open the App Summary page for the app, as described in “To open the App Summary page for an app.”

  4. In the Versions section, click View Details for the current version.

  5. From your Version Details page, click “Ready to Upload Binary.”

    If your app has the status Waiting For Upload, it’s already passed through this step, and you can use Xcode or Application Loader to upload the binary.

  6. If your iTunes Connect record isn’t complete, a message displays at the top of the page to indicate what remains to be configured before the binary can be uploaded.

    Resolve whatever issues remain and repeat step 5.

  7. Answer questions about Export Compliance, and if needed, upload encryption authorization documents.

    Because all apps are loaded on Apple servers in the United States, all apps are subject to U.S. export laws. See Cryptography and U.S. Export Compliance for more details about this step.

  8. Answer questions about Content Rights.

    Indicate whether the app has added third-party content. If you answer yes, you are asked to confirm that you have permission to use the third-party content in each territory in which the app will be available. It’s your responsibility to determine and follow regulations that apply in each territory.

  9. Click Save.

  10. Click Continue on the Application Loader instructions page.

    If you are using Xcode, ignore the Application Loader instructions and instead follow the instructions in “Submitting Your App” in App Distribution Guide. Xcode uses Application Loader to submit the app for you.

    iTunes Connect returns to the Version Details page.

When you successfully complete these steps, your app version status changes to Waiting For Upload. This status allows Xcode or Application Loader to deliver the binary to iTunes Connect. When iTunes Connect receives the app binary, the app status changes to Upload Received. For information about what the status indicators mean and what actions are available for each status, see “About App Statuses.”

Using Xcode

The Xcode development environment is tightly integrated with iTunes Connect. When you are a developer adding an individual app to iTunes Connect, uploading your app binary using Xcode is straightforward and efficient.

When your iTunes Connect record is ready, Xcode receives metadata from the available record. From inside Xcode, you associate your binary with the iTunes Connect record you created for the app and complete the upload.

For more information, see “Submitting Your App” in App Distribution Guide.

Using Application Loader

Application Loader is a tool to help you upload your apps to iTunes Connect. It’s particularly helpful if your app includes In-App Purchase products that need to be configured for the app.

Download, install, and run the Application Loader to upload the binary. You load a .ZIP file for an iOS app or a .PKG file for a Mac app.

bullet
To download Application Loader
  1. Sign in to iTunes Connect.

  2. Click Manage Your Apps.

    ../Art/module_icon_apps_2x.png
  3. At the bottom of the page, click Download Application Loader.

    ../Art/app_loader_2x.png../Art/app_loader_2x.png

For more information, see Using Application Loader.

Cryptography and U.S. Export Compliance

U.S. export laws require that products containing encryption be properly authorized for export. When you’re ready to upload your first binary for your app or upload a binary update, iTunes Connect presents a series of questions regarding software encryption. The questions are designed to determine the level of encryption in the app according to U.S. Bureau of Industry and Security (BIS) classifications. Based on your answers, you may be required to provide one or more of the following documents:

  • Encryption Registration approval from BIS

  • CCATS approval from BIS

  • French import declaration

For more information on BIS requirements for encryption, see the BIS Encryption page.

All apps distributed through the App Store or Mac App Store must go through the encryption review: All apps are uploaded to an Apple server in the United States, which means that your product is exported from the United States and is captured by U.S. export laws. This requirement applies even if you plan to distribute apps only within your own country.

Next Steps: App Review Results

After you upload your binary, Apple reviews the app and the accompanying metadata.

If Apple rejects your binary or metadata, the app status changes to Rejected and iTunes Connect users are notified of the specific issues. In addition to the app status and messages posted at the top of the Version Details page for the app, iTunes Connect provides the Resolution Center for you to communicate directly with Apple regarding issues with the app. See “Using the Resolution Center.”

If Apple approves your app, the app status changes to “Ready for Sale” and iTunes Connect users are notified of the status change. You can track its download progress, as described in “Viewing Sales and Trends.” You can follow comments and issues that users have, as described in “Improving Your Customers’ Experience.”

If, instead, your app status changes to Pending Developer release, the app’s availability date is in the future. You can change the availability date at any time, as described in “Changing an App’s Availability Date.”