Replacing Your App with a New Version

When you’re ready to distribute a new version of your app, you upload the new app binary version into the same iTunes Connect record you created for the app’s previous version. Updated versions keep the same Apple ID, iTunes Connect ID (SKU), and bundle ID as the original version. You can update the metadata used in the store for the new app version and add a description of the new version’s features. Updated app versions are available free to customers who purchased a previous version.

Adding a new version of an app is similar to adding the first version, except that you can set three additional options:

Creating the Next App Version in iTunes Connect

You can add a new version of an app when the current version’s status is “Ready for Sale” or Developer Removed From Sale. The new app version goes through the same review process as the first version.

../Art/up_appsum_new_version_2x.png../Art/up_appsum_new_version_2x.png

Only the team agent or users with an Admin or Technical role can add a new app version. If your user account doesn’t have the appropriate role, you don’t see the Manage Your Apps module on the iTunes Connect homepage. Contact a user in your organization with an Admin role to give you the right access. See “Viewing and Editing iTunes Connect Users.”

bullet
To add an updated version of your app
  1. As an iTunes Connect user with an Admin or Technical role, sign in to iTunes Connect.

  2. On the iTunes Connect homepage, click Manage Your Apps.

    ../Art/module_icon_apps_2x.png
  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 of the App Summary page, click Add Version.

    If the current version of the app doesn’t have the “Ready for Sale” or Developer Rejected status, you won’t see an Add Version button. If the app has not completed the app review process—it has a status such as Waiting For Upload or Waiting For Review—you can replace the binary in the existing version. See “Rejecting Your Binary.”

  5. In the New Version page, enter the new version number and fill in the “What’s New in this Version” field (release notes).

    If the previous version of the app has localized metadata, this page presents sections to include the What’s New information for each of the currently supported languages.

    ../Art/apps_new_version_whats_new_2x.png../Art/apps_new_version_whats_new_2x.png
  6. Click Save.

    A new Version Details page shows you the information you just entered.

  7. Review and update the information to describe the new version.

    The information from the previous version is shown. Review and edit the following sections, as needed:

  8. Fix any errors indicated for the new version.

    If there’s missing information required to save the new version information, you see messages at the top of the page describing the issues. For example, if iTunes Connect has additional requirements since you submitted the previous version, you see messages indicating what new information is required.

    In the section with errors, click Edit and update the values.

    When all errors are resolved, the Version Details page displays “Ready to Upload Binary” in the title bar.

    ../Art/up_ready-to-upload-binary_2x.png../Art/up_ready-to-upload-binary_2x.png

Uploading the New Binary

After you’ve prepared your iTunes Connect record for a new app version, you’re ready to upload the updated binary. There are two ways to upload your binary. Both methods produce the same results:

bullet
To begin the Ready to Upload Binary flow
  1. From your Version Details page, click “Ready to Upload Binary.”

    If your app version has the status Waiting For Upload, it’s already passed through this step.

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

  3. Indicate whether the new app version has added encryption functionality relative to the last version or whether that functionality has been modified or removed.

    If you answer yes, you are asked to answer questions about the level of encryption included in the new version. See “Authorizing for Export” for more details about this step.

  4. Indicate whether the new app version has added third-party content relative to the last version.

    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.

  5. Indicate whether you are updating this app because of legal or usability issues.

    If a previous version of the app is unsuitable for use because of a legal or usability issue, you can indicate the version so that the indicated version won’t be available to users through iCloud. See “Preventing App Versions from Appearing in iCloud.”

  6. Click Continue.

  7. In the Version Release Control page, indicate your preference and click Save Changes.

    You can choose to release the new version as soon as it’s reviewed or to wait to trigger the release yourself. See “Specifying When App Versions Are Released.”

  8. Click Continue in the Application Loader instructional 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.

When you’ve successfully completed 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.

After the binary is uploaded, the new app version status is Waiting For Review. The App Summary page shows the app currently for sale with the status “Ready for Sale” and the version just added. This page will only ever show up to two app versions.

../Art/up_ready_for_sale_2x.png../Art/up_ready_for_sale_2x.png

Preventing App Versions from Appearing in iCloud

You can indicate a legal or usability issue with a version of your app to make sure that the version is excluded from being pushed to existing customers on iCloud. There are two places to make this choice:

  • While you are preparing a new app version to replace the problematic version

  • From the bottom of the “Rights and Pricing” page for the app

If the version of your app whose status is “Ready for Sale” has a legal or usability issue, you must submit an update for the app and indicate the issue with the previous version when submitting the new version.

bullet
To disable a version of an app for availability through iCloud
  1. On your App Summary page, click “Rights and Pricing.”

  2. At the bottom of the page, click “Manage iCloud download settings for this app.”

    A list of the existing versions of the app opens.

  3. Select the app version or versions that you want to disable on iCloud.

    ../Art/ed_indicate_legal_issue_2x.png../Art/ed_indicate_legal_issue_2x.png
  4. Click Save.

If a legal dispute is resolved, you can reenable the app version to be available again on iCloud. Follow the steps in “To disable a version of an app for availability through iCloud” and change the selections.

Specifying When App Versions Are Released

When you upload a new version of an existing app, you can specify when you want to release an app version to the store by using iTunes Connect version release control.

As part of your “Ready to Upload Binary” questions, you are shown the two options for version release control:

../Art/up_version_release_control_2x.png../Art/up_version_release_control_2x.png

If you choose to automatically release your app update, that app is posted to the store as soon as it’s approved by Apple (pending the availability date you have set).

If you choose to control the version’s release, your app status changes to Pending Developer Release after it’s approved by Apple, indicating that you can release it to the store when you’re ready.

bullet
To release a Pending Developer Release version to the store
  1. As an iTunes Connect user with an Admin or Technical role, sign in to iTunes Connect.

  2. On the iTunes Connect homepage, click Manage Your Apps.

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

    You’ll see an action indicator for your new version (indicating that the version is being held for developer release).

    ../Art/up_pending_dev_review_2x.png../Art/up_pending_dev_review_2x.png
  4. Click the View Details button for the new version.

  5. Click the Release This Version button that appears.

    Your app version will then be live on the store pending the customary processing times.

You can release your app version using iTunes Connect Mobile by selecting the app version from the Manage App screen and tapping Release This Version.

../Art/apps_new_version_mobile.png

If you have an app in the Pending Developer Release state for longer than 30 days, you receive an email reminder from Apple. If you decide that you don’t want to release a Pending Developer Release version, reject your binary and submit a new one. See “Rejecting Your Binary.”