Submitting the App to App Review

After you provide app configuration information, as described in Creating an iTunes Connect Record for an App, and uploaded a build, as described in Uploading a Build for an App, you’re ready to choose a a build, validate your app information, and submit your app for review. Note that only users with the Admin, Technical, or App Manager role can submit apps for review.

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

Before you submit your app, you also have the option of having users test prerelease versions of your app. This step is described in TestFlight Beta Testing (iOS, tvOS, watchOS).

Choosing a Build

You can upload any number of builds for your app, and they will remain in Activity on the App Details page. (See Viewing Builds.) When you submit the app for App Review, only one build can be associated with the App Store version of the app you want to submit. The build, called the current build, is the one that will be submitted for App Review.

To choose a build to be the current build, follow these steps:

  1. Open the App Details page for the app, as described in Creating an iTunes Connect Record for an App.

  2. Under App Store, select the version for the platform you want to submit and scroll to the Build section.

  3. Click the plus sign to select a build. The plus sign appears only if you have uploaded builds and have not yet not selected a current build. If you have already selected a build, you can remove it if you want to select a new one. See Removing the Current Build.

  4. A list pops up containing all of the uploaded builds. Select the one you want to choose as the current build.


    If an earlier version of your app became Ready for Sale in the App Store, then the list of builds includes only builds you have uploaded since then. For more detail on which builds are available for you to choose, see Viewing Builds.

  5. After you click Done, the build number appears in the Build section of Versions along with its upload date and time.

  6. Click Save at the top of the page.

Removing the Current Build

You can choose to remove the current build for a version. Removing it does not delete the build from the list of prerelease builds; it just means the build is no longer the current build for that app version.

  1. Open the App Details page for the app, as described in Creating an iTunes Connect Record for an App.

  2. Under App Store, select the version for the desired platform and scroll down to the Build section.

  3. Hover over the build and click the minus sign that appears to the right of the upload date.


Changing builds

You can set and change the current build as often as you want, until you have submitted the app for review, by repeating the steps above for choosing a build and removing the current build.

Verifying App properties

Make sure to configure and validate the following properties that can’t 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 build:

Submitting the App for App Review

When you’re ready to submit the app for App Review, iTunes Connect walks you through a final set of questions. Only users with the Admin, Technical, or App Manager role can submit apps for review.

To submit an app for review

  1. Make sure that you have completed all the configuration the app needs.

  2. Make sure you have uploaded at least one build and selected one as the current build for the app. See Choosing a Build.

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

    Your app’s total uncompressed size must be less than 4GB. Each Mach-O executable file (for example, must not exceed these limits:

    • For apps whose MinimumOSVersion is less than 7.0: maximum of 80 MB for the total of all __TEXT sections in the binary.

    • For apps whose MinimumOSVersion is 7.x through 8.x: maximum of 60 MB per slice for the __TEXT section of each architecture slice in the binary.

    • For apps whose MinimumOSVersion is 9.0 or greater: maximum of 500 MB for the total of all __TEXT sections in the binary.

    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 build 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.

  4. Open the App Details page for the app, as described in Creating an iTunes Connect Record for an App.

  5. On the platform version page under App Store, click Submit for Review at the top right of the page.

  6. 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.

  7. 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.

  8. Answer questions about the Advertising Identifier (IDFA). Indicate whether your app uses the Advertising Identifier, and if so, in what way. See The Advertising Identifier (IDFA) for more details about this step.

    If you submit the app for review again in the future, you will need to fill out the questions again.

  9. Click Submit.

    iTunes Connect returns to the platform version page.

When the submission is complete, the app version status changes to Waiting for Review. For information about what the status indicators mean and what actions are available for each status, see About App Statuses.

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 build for your app or upload a new build, 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, go to Bureau of Industry and Security Encryption webpage.

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.

If your app is not using encryption and you don’t want to have to answer these questions at the time of submission, you can provide export compliance information with your build. You can also provide new or updated documentation via iTunes Connect to receive the appropriate key string value to include with your build before uploading it to iTunes Connect.

To add export compliance documentation in iTunes Connect:

  1. Go to the Encryption section under Features.

  2. Click the plus sign next to the appropriate platform section.

  3. Answer the questions appropriately.

  4. Attach the file when prompted.

  5. Click Save.

For information about adding export compliance keys to your app’s Xcode project, go to the section “Adding Export Compliance Information to Your Project (Optional)” on the “Configuring Your Xcode Project for Distribution” page of Apple’s App Distribution Guide.

Your documents will be sent for review immediately and the status of your document will show in Compliance Review. A key value will also be generated automatically that you can include in your Info.plist file. For more information on including the key value with your build, see the Resources and Help section Trade Compliance.

You can upload a build without an export compliance key. If you include a key, it can indicate that you do not need export compliance documentation; this requires no approval. If you include a key that references a specific export compliance document, that document must be approved; it cannot be in In Review or Rejected.


You can review your answers at any time by clicking the document file name and selecting More Information. If you need to update your documentation or change any of the answers to the questions, you will need to repeat the steps above to add a new document that corresponds with your changes.

The Advertising Identifier (IDFA)

Your app must comply with IDFA usage in order to be approved by App Review. When you’re ready to submit your app, you will be presented with a questionnaire about whether your app uses the Advertising Identifier.


If you check Yes, you will need to supply further details about how your app uses IDFA.


If you checked No but we determine your app does use IDFA, your app will be put into the Invalid Binary status, and you will be notified by email. Similarly, if you checked Yes but your app uses IDFA in ways that don’t match the statements you checked, your app will be rejected by App Review and put into the Rejected status.

In either case, when you resubmit the build, you will be presented with the IDFA questions again and can provide the appropriate answers.

Next Steps: App Review Results

After you submit your build, Apple reviews the app and the accompanying metadata.

If Apple rejects your build 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 App Details page, iTunes Connect provides the Resolution Center for you to communicate directly with Apple regarding issues with the app. See Viewing Resolution Center Communications.

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 and Viewing App Analytics. You can follow comments and issues that users have, as described in Monitoring Reviews on the App Store.

If, instead, you would like to manually release your app version or you have scheduled to release it at a later date, see Specifying When App Versions Are Released.