Adding New Apps
To add a new iOS or Mac app, you use the Manage Your Applications module in iTunes Connect, performing the following tasks:
Entering basic app information and supporting metadata
Setting your pricing and territories
Adding languages and keywords
Uploading a large icon (for iOS apps only) and screenshots
Answering further questions about your binary
Preparing your app for binary upload
Review the terms of your Apple Developer Program License Agreement and make sure that, in compliance with its terms, you own or control all content contained in your app, which includes all the metadata entered here.
After you’ve performed all of these tasks, submit the app using Xcode (as described in App Distribution Guide) or Application Loader (as described in “Using Application Loader”). At that point, you can make changes and update the binary for the app. For more information on editing your app information after the app has been uploaded, see “Editing and Updating App Information.”
Preparing Your App for Binary Upload
You prepare your app for binary upload through the Manage Your Applications page.
Log in to iTunes Connect.
On the iTunes Connect homepage, click Manage Your Applications.
The first time you see the Manage Your Applications page in iTunes Connect, it is blank. After you’ve uploaded your first binary, you see your apps listed here.
On the Manage Your Application page, click Add New App.
If you have contracts in effect for both iOS and Mac apps, select your app type.
If you have signed a contract for only one app type, this page does not appear.
Follow the instructions on the subsequent pages.
On each of the following pages, click Continue to go to the next page or Cancel to cancel adding an app record.
The following sections break down the steps involved in adding an app.
Entering App Information
On the App Information page, you supply (in your primary language) all of the initial app-level information for the app you are creating. If you need assistance as you’re filling out the page, select the Help button (?) next to the field or refer to Table 7-1 for the property descriptions.
Property | Description |
|---|---|
Default Language | The primary language you will be using to enter app details for display on the App Store. The default is English. |
App Name | The name of your app as it will appear on the App Store. The app name cannot be longer than 255 bytes and can be no fewer than 2 characters. |
SKU Number | A unique ID for your app. You can use letters, numbers, hyphens, periods, and underscores. The SKU cannot start with a hyphen, period, or underscore. |
Bundle ID | An identifier used by iOS and OS X to recognize any future updates to your app. Your bundle ID must be registered with Apple and unique to your app. Bundle IDs are app-type specific (either iOS App or Mac OS X App). The same bundle ID cannot be used for both iOS and Mac apps. The bundle ID must exactly match the bundle identifier in your Xcode project |
Bundle ID Suffix | A string that is appended to the bundle ID property (if it is a wildcard App ID) to form a bundle identifier that exactly matches the bundle identifier in your Xcode project |
Follow these guidelines when entering information about your app:
Your metadata and assets should be in your default language.
Apple expects you to upload your metadata and assets in the default language. As a result, your metadata and assets will be displayed in all App Stores worldwide unless you specify individual localizations. The default language you select here is not displayed in the App Store under Languages. You set the information displayed on the App Store in your binary.
Choose an appropriate name for your app.
Do not include a description of your app in the app name. Use the Application Description field instead. After you have submitted the app, its name can be changed only when your app is in an editable state.
Choose a name that is distinct and appropriate. For best results on the application product pages on the desktop App Store, use no more than 70 characters. For the iOS App Store, use no more than 35 characters. Do not choose an app name that is substantially similar to an existing app name (for example, by adding or removing spaces, exclamation points, or other characters).
Ensure that your app name does not violate the trademark or other rights of a third party. If you enter an app name that is trademarked or already in use on the App Store, Apple can remove your app from the App Store.
If you include compatibility language in your app name, for example. “[app name] for iPad,” this compatibility language is not considered the app name for purposes of restrictions on duplicative names or intellectual property rights. In other words, if someone else has the wording “xxxx” on the App Store, you may not submit “xxxx for iPad” as an app name. See Guidelines for Using Apple Trademarks and Copyrights to make sure your compatibility language uses Apple marks correctly.
Create a SKU number that is unique and meaningful to you.
The SKU is any alphanumeric sequence of letters and numbers you’d like to use to be uniquely identified in Apple’s system. You may create any string of UTF-8 letters and numbers, as long as it is unique to your developer account. This SKU is internal only and is not seen by users at any time. After you have submitted your metadata, this SKU is not editable.
The bundle ID (combined with the bundle ID suffix) needs to exactly match the bundle identifier in your Xcode project.
You are required to have an explicit bundle ID for distribution on the App Store. If you choose an explicit App ID from the Bundle ID menu, then it must match the bundle identifier in your Xcode project
Info.plistfile. If you choose a wildcard App ID, you must also specify a bundle ID suffix. The wildcard App ID combined with the bundle ID suffix must exactly match the bundle identifier in your Xcode project.
After you enter the App Information, click Continue to go to the next page.
Setting Territory Rights, Pricing and Availability
You set territory rights, pricing, and availability on the “Rights and Pricing” page.
On this page, you:
Set the date when you want your app to go live on the App Store
Schedule price tier changes for the future (by setting a price tier effective date and a price tier end date)
(iOS only) Offer a discount to educational institutions buying in bulk
Select the territories where you would like to make your app available
If you need assistance as you’re filling out the page, select the appropriate Help button (?) next to the field or refer to Table 7-2 for the property descriptions.
Property | Description |
|---|---|
Availability Date | The date when your app will be available for purchase on the App Store. If your app has not been approved by Apple before this date, it will go live as soon as it has been approved. The date you select is a global date and applies to all territories selected. If you change this date, the new date applies to all versions of your app. If you create a new version of your app, you may use the “Version Release Control” feature to control the date your new version is released to the App Store. |
Price Tier | The level that determines both the customer price and your proceeds (which is the net price after taxes, where applicable, have been taken out). If Price Tier is not Free, you must have a paid commercial agreement in place before you can sell in your chosen tier. If you have a Paid Applications contract in effect, iTunes Connect allows you to schedule price tier changes for your apps over time. For more information, see “Scheduling Price Tier Changes.” |
Price Tier Effective Date | When scheduling price tier changes, the date when the new tier will take effect on the App Store. For more details on scheduling price tier changes, refer to “Scheduling Price Tier Changes.” |
Price Tier End Date | When scheduling price tier changes, the date that the tier will no longer be in effect and will return to the previously set price tier. For more details on scheduling price tier changes, refer to “Scheduling Price Tier Changes.” |
Discount for Educational Institutions (iOS only) | If selected, this app is offered at a discount to educational institutions when they purchase multiple copies at once. The details of the discount are found in the latest paid application agreement, which you must sign before this app will be available to education customers. The discount for educational institutions option is not available for Mac apps. |
Custom B2B App iOS only | If selected, this app is a custom B2B app that is not available in the general App Store. This option is available only if you are editing the first version of your app and it is still in an editable state. An app that is set up as a custom B2B app will only be available to the Volume Purchase Program customers that you specify in iTunes Connect, and it will only be available in the applicable territories. (For example, U.S. Volume Purchase Program customers must use the U.S. App Store Volume Purchase Program for Business.) Custom B2B apps are not available to educational institutions or general App Store customers. To learn more, see the Volume Purchase Program for Business webpage. To learn more about how your customers can sign up for the Volume Purchase Program, visit the VPP for Business Enrollment webpage. For a custom B2B app, you must enter at least one Apple ID that was created for use with the Volume Purchase Program. The app will be available only to the VPP Apple IDs you specify. You can add as many Apple IDs as you would like. |
Territories | The individual countries or territories where you want to sell your app. By default, your app is available in all countries the App Store currently supports. |
Follow these steps to create a custom B2B app that is not available in the general App Store.
On the “Rights and Pricing” page, select the Custom B2B App checkbox.
Click the Add Apple ID button to add an Apple ID.
Enter the Apple ID and type Return.
Repeat steps 2 and 3 for each Apple ID you want to add.
You must add one or more Apple IDs.
Click the close button (x) next to an Apple ID to remove it from the list.
Follow these steps if you want to select individual countries where your app will be sold.
On the bottom of the “Rights and Pricing” page, click “specific stores”.
To sell your app worldwide, click Select All.
To remove your app from all App Store territories worldwide, click Deselect All.
To select specific countries, click the checkbox next to the country name.
For your app to go live automatically when you sign a new Paid App contract for future App Store territory expansions, select the New Territories As Added checkbox.
Click Continue to go to the next page.
Supplying Your App’s Version Information, Metadata, App Review Information, Licensing Agreements, and Uploads
The next page is used to further describe your app and is separated into sections of information. This is the last page you fill in before uploading your binary using either Xcode or Application Loader.
On this page you:
Supply version information
Set your app’s rating
Describe your app more completely by providing metadata
Provide your own EULA if desired
Upload your app’s assets
Supplying Version Information
In the Version Information section, you supply (in your primary language) all the metadata associated with this specific version of your app. This information appears to the user on your app product page on the device (for iOS apps only) and on the desktop App Store (for both iOS and Mac apps). For Mac apps, this information is displayed only on the Mac App Store. If you need assistance when filling out the fields, use the Help button next to each field and menu. See Table 7-3 for version information field descriptions.
Property | Description |
|---|---|
Version Number (required) | The version number of the app you are adding. Numbering should follow typical software versioning conventions (for example, 1.0, 1.0.1, 1.1). Important: Make sure the version number matches the version number set in the bundle. If these do not match, then upload errors for later updates may occur. |
Copyright (required) | The name of the person or entity that owns the exclusive rights to the app, preceded by the year the rights were obtained (for example, 2008 Acme Inc.). Do not include the copyright symbol because it is added automatically. |
Primary Category (required)/ Secondary Category(optional) | The categories that best describes the app you are adding. See “Choosing Primary and Secondary Categories” for a list of available categories. |
Subcategory (optional) | Subcategories for games. See “Choosing Subcategories for Games (Optional)” for a list of available subcategories. |
Choosing Primary and Secondary Categories
Choose the primary category that best describes your app. This is the category under which your app is listed. Choose a secondary category to further define your app if desired. The primary and secondary categories (listed here) are identical.
Books (iOS only)
Business
Catalogs (iOS only)
Developer Tools (OS X only)
Education
Entertainment
Finance
Food & Drink (iOS only)
Games
Graphics & Design (OS X only)
Health & Fitness
Lifestyle
Medical
Music
Navigation (iOS only)
News
Newsstand (secondary category only)
Photo & Video
Productivity
Reference
Social Networking
Sports
Travel
Utilities
Video (OS X only)
Weather
Choosing Subcategories for Games (Optional)
If you select Games as the Primary or Secondary Category, you can optionally select up to two subcategories to help more accurately define your game. Select from a list of subcategories to further organize your game app.
Action
Adventure
Arcade
Board
Card
Casino
Dice
Educational
Family
Kids
Music
Puzzle
Racing
Role Playing
Simulation
Sports
Strategy
Trivia
Word
Setting a Rating
In the Rating section, set the rating for your app for the purpose of parental controls on the App Store. All apps are required to have a rating. For each content description, choose the level of frequency that best describes your app. As you mark each selection, the app rating is displayed on the right. For a description of app ratings, see Table 7-4.
Rating | Definition |
|---|---|
4+ | Apps in this category contain no objectionable material. |
9+ | Apps in this category may contain mild or infrequent occurrences of cartoon, fantasy or realistic violence, and infrequent or mild mature, suggestive, or horror-themed content which may not be suitable for children under the age of 9. |
12+ | Apps in this category may also contain infrequent mild language, frequent or intense cartoon, fantasy or realistic violence, and mild or infrequent mature or suggestive themes, and simulated gambling which may not be suitable for children under the age of 12. |
17+ | Apps in this category may also contain frequent and intense offensive language; frequent and intense cartoon, fantasy or realistic violence; and frequent and intense mature, horror, and suggestive themes; plus sexual content, nudity, alcohol, tobacco, and drugs which may not be suitable for children under the age of 17. |
Table 7-5 provides the equivalent ESRB and PEGI ratings.
Rating | ESRB | PEGI |
|---|---|---|
4+ | EC | 3+ |
None | E | 7+ |
9+ | E10+ | None |
12+ | T | 12+ |
17+ | Mature | 16+ |
No Rating This content will not be sold via iTunes | Adults Only | 18+ |
Entering Metadata
For each field in the Metadata section, enter further descriptions for your app version. Unless specified otherwise, these fields are required. Because users read this description to help them make their purchase decision, it is a key piece of marketing text. For tips on writing an effective app description, see “Best Practices.” See Table 7-6 for descriptions of these properties.
Property | Description |
|---|---|
Description (required) | A description of the app you are adding, detailing features and functionality. Descriptions can be no longer than 4000 characters. |
What’s New in this Version (required) | Release notes detailing what’s new in this version of your app. For example, you might want to list new features, UI improvements, or bug fixes. Cannot be longer than 4,000 characters. |
Keywords (required) | One or more keywords that describe your app. Keywords are used to help customers search the App Store effectively. Your app will be searchable by app name, company name, and keywords. |
Support URL (required) | The support website you plan to provide for users having questions regarding the app. The support URL must lead to actual contact information so that your users can contact you regarding app issues, general feedback, and feature enhancement requests. |
Marketing URL (optional) | The website where users get more information about the app. |
Privacy Policy URL (optional) | A URL that links to your company’s privacy policy. Privacy policy URLs are required for all apps that offer auto-renewable or free subscriptions. Customers see this URL on their invoice and on the subscription confirmation email they receive. |
Follow these guidelines when entering Metadata information:
Use the description property to accurately describe the features and functionality of your app.
Use plain text, not HTML. Line breaks are permitted.
Enable spell check in Safari to catch spelling errors. Apple does not check spelling or grammar.
Don’t use this section to conduct other communication to your users and don’t include keywords; a Keywords field is provided and is detailed below.
Use keywords to help users find your app on the App Store effectively.
Keep in mind that your app is searchable by app name, company name, and keywords. Make sure you choose keywords carefully. After you submit them, you may change them only when you update your binary or when your app status is Rejected, Developer Rejected or Metadata Rejected.
Enter one or more keywords that describe your app. Keywords can be single words or phrases. The text field is limited to 100 characters and must be more than 2 characters.
For best results, separate multiple keywords with commas.
Keywords must be related to your app content and cannot contain offensive or trademarked terms.
You may not use other app names or company names as keywords.
Keywords can be single words or phrases.
Providing App Review Information
Use the App Review Information section to provide contact, review notes, and demo account information so that the App Review team can review your app. If your app requires specific settings, user registrations, or account information before you submit it to the App Store, be sure to include that information in this section. If your app delivers streaming video over the cellular network, enter a test stream URL in this field. You can also include general instructions or other relevant information about your app that you think would be useful for the review process.
Property | Description |
|---|---|
First Name (required) | The first name of the person in your organization who should be contacted if the App Review team has any questions or needs additional information. |
Last Name (required) | The last name of the person in your organization who should be contacted if the App Review team has any questions or needs additional information. |
Email Address (required) | The email address of the person in your organization who should be contacted if the App Review team has any questions or needs additional information. Users do not see this email address. |
Phone Number (required) | The phone number of the person in your organization who should be contacted if the App Review team has any questions or needs additional information. Include the country code. |
Review Notes (optional) | Additional information about your app that can help during the review process. Include information that may be needed to test your app, such as app-specific settings and test registration or account details. The Review Notes field must not exceed 4000 bytes. This text is visible only to the App Review team. |
Username (optional) | The user name for a full-access demo account. This account is used during the app review process and must not expire. Details for additional accounts should be included in the Review Notes field. |
Password (optional) | The password for the full-access demo account |
Providing an End User License Agreement (Optional)
If you want to provide an end user license agreement (EULA) for your app beyond the standard EULA that Apple provides, click the “click here” link in the EULA section.
Enter your agreement in plain text in the EULA Text field that appears. All HTML tags are stripped and escaped, and only line break characters are accepted. Your own EULA must meet certain minimum requirements indicated in your agreement. Click the “minimum terms” link to review these requirements.
When you provide a EULA, you must also select the countries in which your EULA applies. Select countries for which your EULA has been properly localized to meet local legal and language requirements.
If you do not provide a EULA, the standard EULA will be applied to your app and the EULA link will not be shown on the app page on the App Store. Click the “standard EULA” link to read the standard EULA that Apple provides.
Here’s an example of what the Apple-provided EULA looks like on the App Store.
Uploading Icons, Screenshots, and Routing App Files for Your App
In the Uploads section of this page, you upload all of your assets—specifically, your large app icon for iOS apps, your first screenshot (for iPhone/iPod touch, iPad or OS X), the routing app coverage file, and any additional screenshots. Before uploading your assets, refer to “Creating Assets with the Correct Specifications” to prepare your assets for upload if you have not already done so. All assets, except for the additional screenshots and the routing app coverage file, are required based on the device families set in your app binary.
Table 7-8 provides a detailed description of the assets you provide in the Uploads section.
Field | Description |
|---|---|
Large App Icon (required) | The large app icon is displayed for your app on the App Store and, if needed, is used to feature your app on the App Store. To be featured prominently on the App Store, it’s good to provide an attractive, original icon that meets the following requirements for both iPhone/iPod touch and iPad apps:
To preview image files before submitting them, click the filename to view them in a separate window. Note: The small icon (57 x 57 pixels for iPhone/iPod touch, 50 x 50 pixels and 72 x 72 pixels for the iPad) that you include inside the binary are used on the iPhone, iPod touch or iPad home screen when installed. |
iPhone and iPod touch Screenshots (required) | The first screenshot that you upload is the first screenshot that appears on your app product page on the App Store and the device App Store when viewed from the iPhone and iPod touch. Up to four additional optional screenshots can be uploaded. All subsequent screenshots will appear in numbered order on the App Store, in the same order in which they were uploaded in iTunes Connect. Only Newsstand apps can reorder their screenshots after they have been uploaded. For best results, do not include the iPhone status bar in your screenshots, and follow these requirements:
|
iPhone 5 and iPad touch (5th gen) Screenshots (required if app runs on 4-inch Retina display) | If your binary indicates that your app will run on the 4-inch Retina display, you are required to upload at least one of these screenshots. Up to four additional optional screenshots can be uploaded. All subsequent screenshots will appear in numbered order on the App Store, in the same order in which they were uploaded in iTunes Connect. Only Newsstand apps can reorder their screenshots after they have been uploaded. For best results, do not include the iPhone status bar in your screenshots, and follow these requirements:
|
iPad Screenshots (required if app runs on iPad) | If your binary indicates that your app will run on iPad, you are required to upload at least one iPad screenshot. Up to four additional optional screenshots can be displayed along with this first screenshot on the app product page on the iPad App Store. Only Newsstand apps can reorder their screenshots after they have been uploaded. For best results, do not include the iPad status bar in your screenshots and follow these requirements:
|
Desktop Screenshot OS X only (required) | The first screenshot you upload is the first screenshot displayed on your app product page on the Mac App Store. Up to four additional optional screenshots can be uploaded. All subsequent screenshots will appear in numbered order on the App Store, in the same order in which they were uploaded in iTunes Connect. For best results, follow these requirements:
|
Routing App Coverage File (optional) | Routing app coverage files are |
If you are adding an iOS app, you are required to upload a large app icon, iPhone and iPod touch screenshots, and (if your app runs on an iPad) iPad screenshots. If you are adding a Mac app, you are required to upload only one desktop screenshot. You will not be asked to provide a large icon when adding a Mac app because it is contained in your Xcode project and the application bundle that you upload later.
In the Uploads section, click Choose File for the asset you want to upload.
Locate the file and click Choose.
Click Upload File.
If the file does not match the requirements, a message appears at the top of the page.
To preview image files before submitting them, click the image to view them in a pop-up window.
After you have entered all the additional information about your app on this page, click Save. You are then taken to your App Summary page to view your created app in its first state, Prepare for Upload.
The seller name that is displayed for your app in the App Store is associated with the legal entity name of your organization as contracted with Apple. To request a change or update to your seller name, you must contact Apple Developer Support in the iOS or Mac Provisioning Portal.
View App-Level Actions on the App Summary Page
Use the App Summary page to view all available app-level actions for setting up additional information for your app and editing current information. These actions apply to all versions of your app because they are considered app level.
Each available action is detailed in “Editing App Information.” The following are considered app-level items:
Apple ID
Bundle ID
SKU
App Type
Newsstand — App Level Enable/Disable (iOS apps only)
Rights & Pricing
Localizing Metadata, Keywords, and Screenshots
On the Version Details page, you choose additional languages in which you would like to enter your app metadata, keywords for that region, and screenshots for both the iPhone/iPod touch and iPad. This information is in addition to the default language metadata you supplied during your initial app creation.
For example, if you choose to upload new metadata, keywords, and screenshots in French, the text and images appear for users who have their iOS or OS language set to French and in all French-speaking stores you selected on the “Rights and Pricing” page. Your app will also be searchable in all French-speaking stores by the localized keywords you enter.
Adding a New Localization
On the Version Details page (access by clicking View Details for a specific version), in the App Localizations section, click the Choose Another Language drop-down menu.
Choose the language you would like to add.
Click Add This Localization.
Enter the localized metadata for the language indicated.
All information, except the App Description, and Keywords, are prepopulated from your native app, including the screenshots already uploaded. If you choose to add other languages, you must fill in all of the same metadata fields you filled in during the initial app creation. If you do not upload new screenshots, the previous (default language) versions will be used.
To provide new screenshots for your localized territory, click Choose File, locate the files, and click Upload.
Click Save.
If you need to edit localizations that you have already added, you can do so within the same section on your Version Details page. For more details on editing localizations, see “Editing Localizations.”
Viewing Your Localizations
Each new language added will be listed in the App Localizations section in the Choose Another Language drop down menu. To view the metadata and images entered for a specific localization, choose that language from the Activated Languages section in the drop down menu and the information will appear on that page:
Deleting Your Localizations
If you’ve added a localization to your app but no longer want to manage it, you can delete it from your version at any time by choosing the language you want to delete and clicking Delete.
Reviewing Your Version Summary
The Version Summary page is a read-only summary of all the metadata and assets you are about to submit to the App Store. Review the information prior to submitting. Remember that even though you can go back and edit your metadata after it has been submitted, not all metadata attributes can be changed. See Table 10-2 to learn which attributes are editable and when.
Selecting a territory from the Territory drop down menu shows you the metadata as it is localized for that territory.
If you have added other languages, you can review each set of metadata by toggling between storefronts in iTunes Connect.
To view the final size of your app after it has been encrypted for DRM purposes and recompressed, see the Version Summary page.
App Name Expiry
After creating your app and it is in the state Prepare For Upload or Waiting For Upload, you have 180 days (6 months) from your creation date in iTunes Connect to deliver a binary to Apple. If you do not deliver a binary before the 180-day deadline, your app is deleted from iTunes Connect. As a result of this deletion, your app name can be used by another developer and you cannot reuse the app name, SKU or bundle ID. See “Deleting an App” to learn more about the ramifications of App Delete.
All admin and technical iTunes Connect users for your account receive the following email warnings to remind you of apps that are approaching their App Name Expiration date:
150 Day Warning. You will receive an email when you have had an app created for 150 days but have not yet delivered a binary, reminding you that you have 30 more days to deliver your binary or your app will be deleted from iTunes Connect. You will be given an exact date of your deadline in this email.
173 Day Warning. You will receive an email when you have had an app created for 173 days but have not yet delivered a binary, reminding you that you have 7 more days to deliver your binary or your app will be deleted from iTunes Connect. You will be given an exact date of your deadline in this email.
180 Day Deletion Confirmation. You will receive an email confirming that your app has been deleted from iTunes Connect, if you have not delivered a binary before your 180-day deadline.
Ready to Upload Your Binary
After you have completed the app upload preparation steps outlined above, you answer more questions depending on the nature of your binary.
From your Version Details page, click the Ready to Upload Binary button.
To be ready to deliver your binary using Xcode or Application Loader, you answer questions about Export Compliance and indicate whether you are updating your app due to a legal issue. See “Authorizing for Export and Indicating Legal Issues” for more details about this step.
After you complete Export Compliance, if your version is an update to an existing app, continue to the Version Control Release page. If your version is a new app, you will be led straight to the Application Loader Instructional page to learn how to deliver your app through Application Loader.
After you have completed Export Compliance, indicated any legal issues, and supplied your Version Release Control settings (if applicable), your app status changes to Waiting For Upload. This status indicates to the Application Loader software that your app is ready to receive a binary delivery.
Authorizing for Export and Indicating Legal Issues
Export laws require that products containing encryption be properly authorized for export. When you are ready to upload your first binary for your app, you will be asked a series of questions regarding app encryption. You will also be asked questions anytime you add a new version to submit a binary update. Based on the answers to these questions, you may need to provide a copy of the CCATS (Commodity Classification Automated Tracking System) file confirming the your app’s classification.
When updating your app, this page will also ask whether you are updating the app because of a legal issue. If you have this issue, select Yes.
On the Export Compliance page, select Yes or No, depending on whether your app contains encryption. If you do not know or you need more guidance on encryption, click where indicated for further information.
If you selected No to all questions and this is the first version of your app, you are taken to the Application Loader Instructional page to learn how to deliver your binary with Application Loader.
If this is an update to your app, you are taken to the Version Release Control page.
If you selected Yes to the export compliance questions, answer the export compliance questions that appear.
New questions appear depending on your answer to the previous question.
If you are asked to provide a copy of your CCATS file, click Choose File, locate the file (in PDF format), and click Upload File.
Be sure to submit only a CCATS form in this step.
After uploading your CCATS document successfully, you see a green check mark.
Click Save.
Version Release Control
You can now determine when your app updates go live on the App Store. With version release control, you can specify when a version of your app goes live rather than have the version go live as soon as it is approved by App Review.
As part of your Ready to Upload Binary questions, you are shown the two options for version release control:
If you choose to automatically release your app update, it will go live as soon as it is approved by Apple (pending the availability date you have set).
If you choose to control the version’s release, your app status will change to Pending Developer Release after it has been approved by App Review, indicating that you can release it to the App Store whenever you are ready.
When you're ready for your app update to go live on the App Store, you are responsible for releasing your app version to the App Store.
Log in to iTunes Connect.
On the homepage, click Manage Your Applications.
Locate your app, then click its large icon to view your App Summary page.
You will see an action indicator for your new version (indicating that the version is being held for developer release).
Click the View Details button for that version.
Click the Release This Version button that appears.
Your app version will then be live on the App Store pending the customary processing times.
If you have an app in the Pending Developer Release state for longer than 30 days, you receive an email reminder from Apple.
Application Loader Instructional Page
All binaries must be delivered using Application Loader. Before your app status can change to Waiting For Uploaded, you see a message explaining where to deliver your app binary before your status can change to Waiting For Upload.
Click Continue to change your app status to Waiting For Upload. The Waiting For Upload status indicates that your app is ready to receive its binary through Application Loader.
© 2013 Apple Inc. All Rights Reserved. (Last updated: 2013-04-23)