You can also filter this data by app, subscription, and other metrics to analyze performance. View data for downloads of your apps, initiated sales, initiated pre-orders, and estimated proceeds. You can also filter data by date ranges, transaction types, subscription offerings, territories, and other metrics. View your final proceeds for each month, with earnings broken out by territory and currency. See the rates used to convert your earnings from local currencies when available and any taxes and adjustments applied.
You can also download more detailed reports of all transactions, including the number of units sold per app or in-app purchase, for the month. To get started, sign in to App Store Connect. View in English. View Account. App Analytics Find out how customers discover and engage with your app. App Store Performance See how many users discover your app while searching or browsing on the App Store, and find out which apps and websites bring customers to your product page.
When your app is ready for public distribution, submit it to App Store Review. Learn about App Store Review. Choose a price point, offer introductory prices for auto-renewable subscriptions, and even let customers pre-order your iOS or iPadOS app.
Learn more about publishing your app. Get next-day sales and unit data in Sales and Trends, and view details on completed payments in Payments and Financial Reports. View and accept the agreements required to offer apps on the App Store.
Add your bank account and tax information to receive payments, view invoices, and more. Learn more about Agreements, Tax, and Banking.
Offer timely events within your apps and games — such as game competitions, movie premieres, live-streamed experiences, and more — that customers can discover right on the App Store.
Learn more about responding to user reviews. The U. Government defines "non-standard cryptography" as any implementation of "cryptography" involving the incorporation or use of proprietary or unpublished cryptographic functionality, including encryption algorithms or protocols that have not been adopted or approved by a duly recognized international standards body e. There are also several exemptions available in U. All liabilities associated with misinterpretation of the export regulations or claiming exemption inaccurately are your responsibility.
To learn more about encryption export controls, visit the U. The Government of France also controls the import and export of encryption apps distributed in France. Exemptions include Banking and Medical applications.
When you submit a new version of your app, you will be required to answer questions in App Store Connect about your app's use of encryption.
Take the steps below before submitting your app to App Review to ensure that you are submitting the right documentation and to bypass these questions if your app does not use encryption. App Store Connect provides a simple way for you to determine your export compliance requirements by presenting you with a set of questions about your app and where you plan to make it available.
Keep in mind that these questions are not the same questions that are required prior to submitting an app. If you are required to, use App Store Connect to submit your export compliance documentation. Once you've determined that you aren't required to submit export compliance documentation or have uploaded required documentation and received your key from Apple, you can update your Xcode settings so that you don't need to answer encryption questions with each app submission.
App Store Connect provides a set of questions to help you determine if export compliance documentation is required from you, and which forms are needed.
See Export compliance documentation for encryption to understand what documentation you may need to provide. See View and edit app information. If export compliance documentation is required, upload your file using the dialog and take the additional steps. If no documentation is required, update your Xcode settings to let us know that your app doesn't use encryption or is exempt from providing documentation. If you are required to upload export compliance documentation, you can use the App Store Connect Encryption section to do so before you submit a build to App Review or TestFlight App Review.
Before you provide this documentation, populate certain app information—app description, territories where you intend to distribute your app, and price—in order to avoid delays in approving your documents.
Apple evaluates export compliance reviews on a case-by-case basis. If complete information is provided, Apple expects to be able to review and clear apps in approximately two business days. Once your documentation is approved, Apple will provide you with a key value to enter in Xcode. If you have specific questions about Apple's export process, contact us. The new version will be available free to customers who purchased a previous version.
You can only create a new version if the current version status is Ready for Sale or Developer Removed from Sale. Keep in mind that it's not possible to revert to a previous version on the App Store if you have an issue with your app. You must create and submit a new version. When you create a new version, the metadata from the current version is transferred to the new version automatically.
For a description of the version properties, go to Platform version information. In Xcode, increment the build string before you upload your build to App Store Connect, as described in Set the version number and build string.
When you are ready to submit your build, add it to your latest App Store version , then submit your app to app review. You can add platforms to an app to create a universal purchase. Note: A watchOS app with an iOS companion app is already included in the same Xcode project as the iOS app, so you don't need to add it to a universal purchase.
Learn how to add watchOS app information. A version for the platform appears selected in the sidebar with the version number 1. You can change the version number in the Version section under General App Information.
When you add a platform, metadata from the existing platform version is transferred to the new platform version, except for the promotional text, description, and screenshots. You can delete a platform if a build has never been uploaded for the platform you wish to delete. Additionally, at least one existing platform version needs to be in an editable app status. See App and submission statuses.
If the criteria is met, hover over the platform you wish to delete and click the delete button — that appears to the right of the platform. You can transfer the ownership of an app to another developer without removing the app from the App Store. The app retains its reviews and ratings during and after the transfer, and users continue to have access to future updates.
Additionally, when an app is transferred, it maintains its Bundle ID — it's not possible to update the Bundle ID after a build has been uploaded for the app. Note: If you initiate an app transfer after December , or accept an app transfer initiated after December , you will not be able to enroll in the App Store Small Business Program or will no longer be eligible to participate in the program. The app must meet specific criteria to be transferable.
For example, at least one version of the app must have been released to the App Store. For more criteria, go to App transfer criteria. Because an app is removed from your account after an app transfer, you should back up all information about the app before you transfer it.
The Account Holder user in your organization initiates the app transfer. Go to Initiate an app transfer. The Account Holder in the recipient organization accepts the app transfer. Go to Accept an app transfer. Before initiating a transfer for an app that offers auto-renewable subscriptions, generate an app-specific shared secret.
Then, share the code with the user of the developer account you are transferring the app to. After sharing the code, initiate the app transfer. Before you accept an app transfer for an app that offers auto-renewable subscriptions, obtain the app-specific shared secret from the initiator, so that you can update your servers to use the code to verify auto-renewable subscriptions.
Once the app transfer is complete, generate an app-specific shared secret so that users outside of your organization no longer have access to it. Keychain sharing continues to work only until the app is updated.
Therefore, the keychain needs to be rebuilt when submitting an update. If the keychain group is defined in the Xcode project, it must be replaced with a keychain group created by the recipient that includes the recipient's Team ID for the app to continue using keychain sharing.
After users update their app, it will not find an authentication token in the keychain and will ask for a one-time re-login. Apps that are part of a Game Center group are removed from the group during the transfer. After the transfer, all leaderboards and achievements revert back to their original status. Leaderboards that were originally a group leaderboard retain the grp. Leaderboards that were originally single leaderboards but were merged into a group lose the grp.
They also revert back to the original leaderboard IDs they had before the merge. Make sure you update the app build with the new leaderboard IDs so that scores are posted correctly. It is important to make a record of your app bundle information before you transfer the app.
If you transfer an app that uses Apple Pay, the merchant ID is not transferred along with the app. Transactions continue to be successful as long as the original certificates are valid. As part of preparing your data for the recipient team, you will need to generate a transfer identifier for all users in your database prior to initiating a transfer.
You can generate the transfer identifier for your users at any time via a REST service endpoint provided by Apple. If you have grouped your apps for Sign in with Apple, you will need to ungroup related apps before initiating a transfer.
To learn how to do this see Group Apps for Sign in with Apple. The Services ID associated with an app that has configured Sign in with Apple will also be transferred. If you do not want the Service ID to be transferred, you can remove its association to your app before you initiate the transfer. In order to transfer apps created with Mac Catalyst that are not offering universal purchase , both the iPad app primary app ID and the Mac app Mac Catalyst app ID need to be transferred.
You will need to initiate the transfer for your iPad app first, and then the associated Mac app after. It is important to transfer the Mac app Mac Catalyst app ID to the recipient as well, as they will not be able to create a new Mac app based off of the iPad app primary app ID. If your app distributes Wallet passes that require ongoing updates from your app or web service, the passes will eventually need to be reissued using a new identifier after transfer is complete so they can be signed with certificates issued from your Apple Developer account.
To minimize user confusion and avoid interruption, we recommend providing a message in your app to let users know that their previously issued pass will become inactive and to download a new pass from your app or web service. See Getting Started with Apple Wallet for details on distributing, updating, and accepting passes. See the Alerts section of the Human Interface Guidelines for best practices on setting alerts. The transferor is responsible for exchanging the actual code set and build assets directly with the recipient.
Be sure to inform the recipient about any capabilities or App Store configuration added to the app, such as keychain sharing, Game Center , or push notifications, so these are maintained in future updates. Keep in mind that regardless of app ownership status, new or additional promo codes do not become available after an app has been transferred. Only promo codes can be generated per app version, and are valid for four weeks from the day they are generated.
If you transfer your app, you will continue to have access to information for payments and sales that occurred prior to the transfer. You will not be able to access information for sales after the transfer has been completed. The recipient of the transferred app will only receive payment and sales information for transactions that occurred after the transfer. When you transfer an app from your account to someone else, you will no longer have access to the app's data in App Analytics.
You can find the historical data of the app in Sales and Trends. If someone transfers an app to you, you'll see all analytics data starting April 1, , or since the app was first made available on the App Store, whichever occurred later. The app should have one of the following app statuses :. Prepare for Submission. Developer Removed from Sale.
TestFlight beta testing should be turned off for all beta versions of the app. You must remove all builds and testers from the app you want transferred and clear each information field below Test Information. All Xcode Cloud related data from the app you want transferred must be removed. Before you begin, you need the Apple ID for the Account Holder in the receiving organization and to meet the criteria for an app transfer. Go to App transfer criteria.
Note: Because an app is removed from your account after an app transfer, you should back up all information about the app for your records. Required role: Account Holder. See App transfer criteria for details on how to resolve common issues. After you initiate the transfer, the app stays in its previous status, with the Pending App Transfer status added, until the recipient accepts it or the transfer expires after 60 days.
Any open App Review communications are closed. The transferor and the recipient can cancel an app transfer in Agreements, Tax, and Banking while it is still in the Waiting for Recipient state. To cancel the transfer, the transferor must click Cancel Transfer next to the app in the App Transfers section of the Agreements tab.
Go to Agreements, Tax, and Banking. You will see an app transfer alert in the Agreements section. In the User Access section, indicate whether you want to give all users on your App Store Connect team access to the app or limit access to just Admin and Finance roles.
Once the transfer is complete, you can limit access to specific people. In the App Privacy section, if the previous owner already disclosed what data the app collects and how it may be used, you will have the option to either keep existing responses to privacy questions or clear responses and answer the privacy questions yourself. You can view the existing privacy details by clicking View Existing Details.
It can take up to two business days for the app transfer to complete, during which the app status is Processing App Transfer.
The recipient can cancel the transfer by clicking Review next to the app in the App Transfers section and clicking Decline on the App Transfer page. When the transfer is complete, you own it. To remove an app from your main view in My Apps, it must be first removed from the App Store and any associated in-app purchases must be removed from sale.
Additionally, you can only remove apps if all versions of that app are in one of the following states:. If the app is part of an app bundle and hasn't been approved yet, it must be removed from the bundle before it can be removed from your main view in My Apps.
App bundles cannot be removed. Removed apps can only be restored if the name is not currently in use by another developer account. Required role: Account Holder , Admin. Scroll to the Additional Information section, then click Remove App. In the dialog that appears, choose Limited Access or Full Access. If you select Full Access, all users will have access to the app. Users with the Admin, Finance, and Access to Reports roles will always have access to all apps. Then click Restore.
If the app name is no longer available, the app cannot be restored. If you believe an app is preventing you from using your trademark as an app name on the App Store, you can submit a claim. Choose Limited Access or Full Access. You provide an App Store icon, three app previews, and 10 screenshots of your app for your App Store product page. You must provide an App Store icon , which is used to represent your app in different sections of the App Store.
For details, go to Add an App Store icon. You must upload at least one screenshot of your app, and uploading an app preview is optional. There are two ways to upload your screenshots and app previews to the App Store. For screenshot specifications, go to Screenshot specifications or App preview specifications. To create and upload an app preview, you must have:. A device running iOS 8 or later for the 5. You set the app preview poster frame , which is the image that displays to customers on the App Store.
You can remove an app preview at any time, but upload an app preview only when the app status is editable. For iOS apps, you can upload app previews in Landscape or Portrait mode. When the customer plays the video, the app preview rotates to the native orientation. For macOS and tvOS apps, you can only provide app previews in landscape. To create an app preview, go to Creating Videos for App Previews.
To change your App Store icon after you published your app on the App Store, you must create and upload a new version and Submit for review. After you add icons in Xcode, upload the build to App Store Connect. Upload up to three app previews and up to ten screenshots. If your app is the same across multiple device sizes and localizations, simply provide the highest-resolution screenshots required. For iPhone, screenshots for 6.
These screenshots will scale down for smaller device sizes. For iPad, screenshots for Whether you choose to use higher-resolution assets to cascade down to smaller device sizes, or use an individual set of assets for every device size, you must use the same option for both your app previews and screenshots per localization. If your app uses the Messages framework or WatchKit, additional screenshots are required.
For macOS and tvOS apps, a separate set of screenshots is required. You can rearrange the screenshots and app previews when you edit the app record, but app previews will always appear before the screenshots. Screenshots and app previews can be uploaded only when the app status is editable. Optionally, click View All Sizes in Media Manager to view the high-resolution screenshots scaled for the other device sizes. After you submit your app for review and your app is approved, you need to create a new version to update screenshots.
You can remove an app preview at any time but remove screenshots only if the app status is editable. For the statuses that are editable, go to App and submission statuses.
If you want to remove it for a specific localization, in the upper-right corner, choose the language from the pop-up menu. Hover over the screenshot or app preview that you want to delete, and click on the Delete button —.
Keep in mind that if a screenshot or app preview is used for other device sizes or localizations, it will be deleted in all places. An app preview poster frame can be edited only when the app status is editable. Use the playback controls to navigate to the frame of the video you want to use for your poster frame. To select the currently displayed frame of the video as your poster frame, click Set Poster Frame. After you add an app to your account , you can upload a build with one of several upload tools see Upload tools.
You can upload more builds as your app changes, distribute a build for testing , or submit your app for review. The first time you upload a build, a beta version of the app is created in your account.
Each time you upload a build, the bundle ID and version number located in the app bundle are used to associate the build with the app and version record in App Store Connect. The build string is used to uniquely identify the build throughout the system.
For details, see Xcode Cloud documentation. You can view all the builds you upload for an app and metadata for each build, including the size of variants created by the App Store. Some builds may not appear after the app is released on the App Store. Note: Builds are organized by version number. View the builds you uploaded for each version by clicking the Versions tab and then the disclosure triangle next to the version number.
To view build groups, click the Build Groups tab. To view the build metadata, click the app icon or build string that appears in the Build column.
The Build Metadata page shows the file sizes of a build , the build type, whether the build contains an iMessage extension, and other build information. After you upload a build to App Store Connect, it goes through a process called app thinning , which creates variants of your app for different devices and operating system versions. The added encryption and DRM affects the ability to compress your binary, and as a result you may see a larger App Store file size for your binary than the binary you uploaded in App Store Connect.
The exact final size for your app cannot be determined in advance to the accuracy of a single byte. On the right, in the Build column, click the app icon or build string for the build you want to view. The device type is the target device for the variant. Universal refers to the variant that runs on all supported operating systems and target devices that are delivered to customers running iOS 8 and earlier, apps purchased in volume through Apple School Manager and Apple Business Manager or through Mobile Device Management MDM , or apps downloaded using iTunes The download size is the compressed size of the app that is downloaded over the air, using cellular bandwidth or Wi-Fi.
If any of the device variant sizes exceed the MB over-the-air download limit, a yellow warning appears next to the build string in the Builds table and next to the variant size in the App Store File Sizes table.
Click the warning icon to read the full warning. Apple will also send you an email with this information. The App Store uses your build settings to calculate the the minimum version of the operating system required for your app to run.
Before you submit an app to App Review , you choose which build from all the builds you uploaded for a version that you want to submit. You can associate only one build with an App Store version. However, you can change the build as often as you want until you submit the version to App Review. If you see a build, remove the build first. If an earlier version of your app has the status Ready for Sale in the App Store, then the builds list includes only builds you have uploaded since that version became available.
For details on which builds are available, go to View builds and build metadata. In the Build section, the app icon, build string , and upload date and time appears.
Note: If you have selected a build that shows Missing Compliance Information, you will need to answer the Export Compliance Information questions before you can submit for review. Click on Missing Compliance next to the build and answer the questions or follow the steps in Upload export compliance documentation. Hover over the build and click the Delete button — that appears to the right of the upload date. TestFlight beta testing lets you distribute beta builds of your app to testers and collect feedback.
You can enable TestFlight beta testing for up to apps at one time in your App Store Connect account. Learn more. Make improvements to your app and continue distributing builds until all issues are resolved before you submit your app to the App Store.
Testers who are invited to test your app will be able to test both the beta app and the App Clip. Only the app or the App Clip can be installed on a device at one time, but testers may choose to switch between the two at any time.
Enter test information about your app, such as a description and feedback email. You will need this if you plan to distribute your build to external testers persons outside your team. Upload your build to the App Store.
Read Cryptography and U. Export Compliance to determine if you need to provide export compliance documentation for your app. After builds are uploaded, they are available for testing for 90 days.
You can create groups for internal and external testers, then assign specific builds to them. After you've added builds to a group, you can add external testers up to 10, people and internal testers up to App Store Connect users with access to your content to test your app. If you invite external testers, the build needs to be approved by TestFlight App Review before testing can begin. Testers install the free TestFlight app on their devices.
Then they use their invitation email or a public link to accept invitations, install your app, send feedback, and get updates. Testers download and install thinned variants of your app.
You can also resend email invitations to testers who have not yet accepted their invitation. Testers running TestFlight for iOS, version 2. This is also available in TestFlight for Mac. You can view this tester feedback in the Feedback section in App Store Connect. Testers running tvOS or earlier versions of iOS can send feedback to the email address you specified in step 1. When you are done testing, you can optionally expire a build to stop testing it, and then go to Overview of publishing an app for the process of submitting your app to the App Store.
Your build will become unavailable in TestFlight after 90 days. To make your beta builds available to external users, your beta build may require review. When you add the first build of your app to a group, the build gets sent to TestFlight App Review to make sure it follows the App Store Review Guidelines. A review is only required for the first build of a version and subsequent builds may not need a full review. Testing can begin once a build is approved.
If you distribute your app to external testers, you need to enter additional TestFlight test information about your app for TestFlight App Review. You can enter this information when you add your app to your account or before you invite external testers. The information you enter for your beta app can be different from the information you enter later when submitting your app to the App Store.
In the Feedback Email field, enter the email address that testers can use to contact you through the TestFlight app. This is also the reply-to address in email invitations to testers. You can update this information anytime and testers will see the updates in the TestFlight app. If your app contains an App Clip, you can add up to three invocation URLs to launch different experiences. Testing of other invocation methods is not currently supported.
To view tester feedback for your App Clip Experiences, see View tester feedback. On the right, in the Builds column, click the app icon or build string for the build that has the App Clip you would like to test. The page opens with the Test Information tab selected. Note: An App Clip Experience can be launched and tested in TestFlight as long as an App Clip is added to the build, but if you want to provide defined experiences, you can add up to three invocation URLs.
On the right, in the Build column, click the app icon or build string for the build that has the App Clip invocation you would like to delete. The page opens with Test Information tab selected. Create a group and add up to internal testers App Store Connect users with access to your content to test your app using TestFlight beta testing. You can choose to automatically distribute builds to internal groups or add them manually. In the dialog that appears, enter the name for a new internal group, then click Create.
You can change the name later, if needed. If automatic distribution is not enabled, all builds must be manually added to the group. If you have builds available for testing, the users you select will receive an email inviting them to test the app. Internal testers can download and test all builds for 90 days. Enter the What to Test information and optionally enter localized versions of test information in the fields under each language-specific section. Note: This information will be available to testers in all groups that have access to the build.
If you have builds available for testing, the users you selected will receive an email inviting them to test the app. The users will be directed to accept the invitation using the TestFlight app on their device or via a redemption code.
Internal testers will be able to download and test all builds for 90 days. To make your build available for external testing, create a group, add builds, and then invite testers using their email address or by sharing a public invitation link.
Note: Enter test information such as Feedback Email and Contact Information if these details have not yet been provided in the Test information dialog. Optionally, enter localized versions of testing information in the text fields under each language-specific section.
If you leave this checkbox deselected, you will have to manually distribute the build to testers after it's approved by TestFlight App Review later. You can only have one build of each version in review at a time.
Once that build is approved, you can submit additional builds. After you submit your build to TestFlight App Review, Apple reviews the build and the accompanying metadata. The first build you submit requires a full review, but later builds for the same version may not. If Apple approves your build for TestFlight beta testing, users on the App Store Connect account with the Admin role will receive an email notifying them of the approval.
If Apple rejects your build or metadata, the external status will be Rejected and you can click status to see rejection details. Once you have builds available to test, and you've added them to a group, you can invite testers. Under Tester Count, click Set Limit to limit the number of testers that can join this testing group using the public link.
Enter a number between 1 and 10, Keep in mind that anyone can share this link, so testers may be able to join your testing group even if you don't invite them directly. If a tester joins your group using a public link, their name and email will not be displayed in the Testers section in App Store Connect it will display as anonymous , but you will be able to see their installation date, sessions, and crashes.
You can disable the public link at any time. In the pop-up menu that appears, choose an option. You can add new testers using their emails address, existing testers you've previously added, or import testers from a CSV file. Testers you invite will get an invitation email to start testing. If a tester accepts an email invitation, their name, email address, installation date, sessions, and crashes, will display in the Testers section in App Store Connect.
The build status changes to Testing. The external testers will receive a notification directing them to accept the invitation using the TestFlight app on their device. In the dialog that appears, confirm you want to remove the build from the group and click Remove. If you want to remove a build from testing for all your testers, go to Stop testing a build.
To appeal your beta build being rejected, contact TestFlight App Review. If you use TestFlight beta testing , you can view information about testers and measure tester engagement. In the Status column, view the status of testers. If a user was invited with an invitation email, their name and email address will display. If a user was invited with a public link, they will display as anonymous. The tester accepted the invite. You can resend email invites to testers who have not yet accepted.
In the Sessions column, view the number of times the app has been in the foreground for at least two seconds. To view crash reports for TestFlight builds in the Crashes organizer in Xcode, click Open in Xcode 13 next to each piece of crash feedback on the Crash Feedback page on the TestFlight tab. Data points such as Status, Sessions, and Crashes are not included.
Additionally, testers invited with a public link are not included in the CSV since their first name, last name, and email address is anonymized. Note: If you have testers that were added by both email and public link, first select the invitation type you would like to remove testers from.
Note: If a tester has a build installed, they will have access to the build until it expires. You'll need to create a group before adding it to a build. All testers in the group will have access to the build. On the right, select a build by clicking the app icon or build string for the build from either the Versions or Build Groups tab. Under either Groups or Individual Testers, hold the pointer over the group or individual tester you want to remove, then click the Delete button — that appears to the right of the table.
All eligible builds are automatically available to users in the App Store Connect Users group. See Remove testers from a group to remove a user from this group. This is set at the group level and will apply to all builds within the tester group. In the table on the right, view the build status and metrics for versions and build groups. In the Status column, view the status of a build. In the other columns, view the number of invited testers, number of installations on devices, and the total number of sessions in the last seven days across all testers.
In the Crashes column, view the number of times the build crashed on tester devices. In the Feedback column, for iOS builds, view the number of feedback submissions you received from your testers. TestFlight testers automatically share crash logs with developers. To view crash reports directly in Xcode for apps distributed using TestFlight, click Open in Xcode 13 next to each piece of crash feedback on the Crash Feedback page on the TestFlight tab.
Feedback submitted by testers running TestFlight 2. This includes screenshots, comments related to crashes, and general comments. Testers running TestFlight 2. Note: If a tester was invited with an invitation email, their email address displays in the detailed feedback view. If a tester was invited with a public link, they display as anonymous, unless they entered their email address when submitting feedback.
The email address only displays for that particular piece of feedback. See Beta tester feedback to learn more about the additional information that is available in the detailed feedback view. You can filter your view by app platforms, OS versions, devices, app versions, build groups, or builds.
Click on the feedback to view the full screenshot and what testers had to say about their experience. Tester, app, and device information is also available in the detailed feedback view. See Beta tester feedback to learn more. In the upper-right corner, click the download icon to download the feedback as a. This file will include the screenshot and the comments associated with the screenshot.
Click on the feedback to read what testers had to say about their experience. Note: Click Open in Xcode 13 next to the feedback to view crash reports in Xcode. In the top-right corner, click the download icon to download the feedback as a. This file will include the crash report and comments associated with the crash.
The tester will be removed from TestFlight.
0コメント