Posted by qwertz Add a Comment. I'm also wondering about this. Did any of you find a solution? Posted by tobias. This question is relevant for me as well. Posted by Cococo games. I have the same question. Posted by mvIOSDev. Hey, Did anyone find a solution to this? Posted by petar I contacted support. It's very weird logic, but now in October this is how it works.
Hope, I could help. Fun Rob Games. Posted by fun rob. Using the app was seamless. The service was great. Will use again when over there! This is the worst delivery experience I have ever had. Not only did my order never arrive, but every time I speak to someone, they leave the chat before we finish talking. And when I do speak to someone, they kept finding different reasons to blame me for my order not arriving and in the end they never returned any of my money.
I even spoke with one of the delivery guys for one of my orders and he said he never went and the order was canceled but their support tells me he went and waited outside for 20 minutes so they have a right to keep my money for their losses. They even asked me for proof that I was actually speaking to the delivery guy rather than review the report he sent. If you buy with this app, be very careful and expect to lose money with orders ever now and then.
I will never buy with these people again. The following data may be used to track you across apps and websites owned by other companies:. The following data may be collected and linked to your identity:. The following data may be collected but it is not linked to your identity:. Privacy practices may vary, for example, based on the features you use or your age.
Learn More. App Store Preview. Description Yummy es la primera App de delivery de comida en Venezuela con mas de comercios disponibles. Apr 7, Version 5. Ratings and Reviews.
Enter testing information and invite testers in App Store Connect by adding their names and email addresses or by sharing a public invitation link. Later, you can make improvements to your app with periodic app updates. After you publish your app on the App Store, you can respond to customer reviews, distribute promo codes, bundle multiple apps in a single purchase, transfer your app to another organization, and more. You can gain insights into the performance of your app by viewing App Analytics data, Sales and Trends reports, and monthly financial reports in Payments and Financial Reports.
View in English. Contact us Support. User accounts and roles overview Add and edit users Change user app access Role permissions Create a sandbox tester account Managing agreements, tax, and banking information To sell apps on the App Store, the Account Holder needs to sign the Paid Applications Agreement in Agreements, Tax, and Banking.
Add a new app View and edit app information Localize App Store information App information Required, localizable, and editable properties Set your developer name on the App Store Uploading app previews and screenshots You can upload app previews and screenshots of your app to demonstrate its features, functionality, and user interface through images and a short video, which will be displayed to customers on your App Store product page.
App Store icon, app preview, and screenshots overview App preview specifications Screenshot specifications Upload app previews and screenshots Uploading your app Once your app details have been entered in App Store Connect, you can upload a build using Xcode or altool.
What is app thinning? Create an in-app purchase In-app purchase information In-app purchase statuses Workflow for configuring in-app purchases Overview of auto-renewable subscription group setup Create an auto-renewable subscription Auto-renewable subscription information Beta testing Before releasing your app on the App Store, use TestFlight to distribute your beta apps and app updates to testers for valuable feedback.
I am being urged to convert to Apple Pay. But it seems the only way I can clarify this is to wait on emailed responses. It would be nice to be able to speak with someone over the phone. Very frustrating. I have been told Apple Pay charged much higher fees. Why would I switch to Apple Pay if it will cost more money?
Both are respectable payment processing systems. I will be very upset if I am forced to switch. The following data may be collected and linked to your identity:. The following data may be collected but it is not linked to your identity:. Privacy practices may vary, for example, based on the features you use or your age.
Learn More. App Store Preview. Screenshots iPhone iPad. Dec 7, Version 1. Ratings and Reviews. App Privacy. Information Seller Apple Inc. Size Category Developer Tools.
In the Localized section, hover over the language you want to delete and click the Delete button —. You can change the primary language for an app. In order for a language to be selectable as a primary language:. You must already have added the language to a previous version. The new language must be approved by App Review. If the language has not been approved, submit a version with this localized metadata to be approved. Then, select it as your primary language on a subsequent update.
You must already have uploaded screenshots for that language that were approved by App Review. See Add screenshots and previews for other device sizes and localizations. These can be either iOS apps with a watchOS app or watch-only apps. You also need to provide screenshots for Apple Watch and an App Store icon.
Your screenshots and icon will be reviewed by App Review after you submit your new app version. Scroll down to the Apple Watch section and if necessary, click the disclosure triangle to reveal the icon and screenshot well. See Screenshot specifications. Note: iOS screenshots are also required for apps with an iOS component, but not required for watch-only apps.
You can use the Messages framework to create sticker packs or iMessage apps that will be available on the App Store for iMessage. These can be standalone apps or app extensions within a containing iOS app. For more information, see iMessage Apps. If your app is an iMessage app, sticker pack, or an extension of one of the two, you add your app to App Store Connect , and then add additional information specific to your iMessage app or sticker pack. Keep in mind that you must also submit an App Store icon in addition to the iMessage app icon.
Scroll down to the iMessage App section and if necessary, click the disclosure triangle to reveal the well. If you want to change the type of iMessage app you offer, you may need to create and submit it as a new app. Currently, sticker packs or iMessage apps can be offered as either:.
Extensions to an iOS app : there is a containing iOS app with additional functionality outside of iMessage. You may rebuild your standalone iMessage app as a standalone sticker pack and vice versa, or rebuild your iMessage extension as a sticker pack extension and vice versa, and submit it as a version update to the same app record in App Store Connect. To rebuild your app from a standalone app to an extension of an iOS app or vice versa, you will need to create it as a new app.
If your practices change, update your responses in App Store Connect. For more information on privacy and data, see User Privacy and Data Use. For more information on responding to app privacy questions, see App privacy details on the App Store. In the dialog that appears, indicate whether you or your third-party partners collect data from your app. If your app is currently available on the App Store, make sure your responses reflect the data collected only from that app version.
Click into each data type and answer the questions that follow. Do this for every data type you selected. After you have finished answering the questions for each data type, you will see your summarized responses under each data type section. To view product page preview details, click See Details. In the dialog that appears, confirm that you agree that your responses are accurate, in compliance with App Store Review Guidelines and applicable law, and that you will promptly update your responses if your data practices change, and click Publish.
If your app is not yet live on the App Store, these responses will be published once your app goes live. Updates to data types will be published after you click Publish. Update your selections for all of the data you or your third-party partners collect from this app. If you removed an existing data type, click Publish. If you added a new data type, click Continue and complete setup for the newly added data type by clicking into the new data type and responding to questions that follow.
Once you have completed responding to the questions, click Publish. If you added a new data type and removed an existing data type, click Publish and Continue. You will need to complete setup for the newly added data type by clicking into the new data type and responding to questions that follow. To edit existing responses, on the right, click on the data type you would like to update your responses for.
If your app uses, accesses, contains, implements, or incorporates encryption, this is considered an export of encryption software, and is therefore subject to U. Using proprietary or non-standard encryption algorithms. 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. For the required and localizable properties, refer to Required, localizable, and editable properties. 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. 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.
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 before the transfer, you will need to generate a transfer identifier for each user in your database. If you have grouped your apps for Sign in with Apple, you will need to ungroup them before initiating the transfer.
The Services ID associated with an app that has configured Sign in with Apple will also be transferred. Initiate the transfer of your iPad app first, and then the associated Mac app. 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. Learn about distributing, updating, and accepting passes. Learn about best practices for setting alerts. 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. 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. 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. Screenshots and app previews can be removed only when the app status is editable. 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 can view all deleted testers by using the Deleted Testers filter from the All Testers menu above the table of testers. 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. You can also quickly add a tester group to a build directly in 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. You can also quickly remove a tester group from a build directly from the builds table. In the dialog that appears, click Remove. 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 and in the Groups column, view the tester groups that are testing the 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. Removed testers may be re-invited to test your app. You can disable the ability for tester groups to take a screenshot and submit feedback from your beta app and provide additional details about a crash.
If you decide you want to receive feedback directly from your beta app and feedback related to a crash again, you can re-enable it. All testers will still be able to send email feedback from the TestFlight app. To enable feedback, click Enable below Tester Feedback. In the dialog that appears, select Enable. If a tester is a part of multiple groups, and one of the groups has feedback disabled, they will only be able to submit email feedback from the TestFlight app.
You can answer the required export compliance questions in the TestFlight section. In the table on the right, in the Build column, click the app icon or build string for the build that is missing compliance information. Internal testers and external testers will no longer be able to install this build. Each app can have multiple versions, and each version can have multiple builds. To publish your app on the App Store, choose which build to submit to review.
You must set a price and set a tax category for your app. Although your app is available in all App Store countries and regions by default, you can select specific regions for your app instead. You also have the option to publish your app as a pre-order.
You submit your app for review to start the App Review process and to make your app available on the App Store. Before you submit an app, enter all the required metadata and choose if you want to release your app manually or automatically, or if you want to release your app in phases. After your app is approved, you can request promo codes to distribute to users before you make your app available on the App Store.
You can distribute the promo codes by email or other means, and the user enters the promo code when purchasing the app. After you submit the app, the app status changes to Waiting for Review. If there are any issues with your app, read and reply to App Review communications. After your app is approved, it can take up to 24 hours to go live on the App Store.
Before you submit your app for review, you must set a price for your app, which will be used for all App Store territories. You can refer to Exhibit C of your Paid Applications agreement to see the currency used by a specific App Store territory. Before releasing your app on the App Store for the first time, you can choose to offer it as a pre-order.
Customers can see your product page and order your app before it's released for download. Once your app is released, customers will be notified and your app will automatically download to their device. For paid apps, customers will be charged before download. Free or paid apps on all Apple platforms are eligible to use this feature.
In-app purchases cannot be set up for pre-order, but you can set up your in-app purchases , including promotional metadata, in App Store Connect prior to and during the pre-order period so that everything is ready once your app is released for download. Promoted in-app purchases will not display on your App Store product page until your app is released for download.
To make your app available for pre-order, select the appropriate setting and submit your app, build, and metadata to App Review. After your app is approved, you can publish it as a pre-order on the App Store. Your pre-order will be available in all territories where your app is available. While your app is available for pre-order, you can update your app by creating and submitting a new version.
The new version must be approved before it can be published as a pre-order on the App Store, so be sure to follow the App Review Guidelines. If you submit a version update during the pre-order period, customers will receive the latest version published to the App Store once your app is released for download.
You may also adjust the price of your app during the pre-order period, but keep in mind that if you change pricing, customers will be charged the price that is lower — the price they accepted for pre-order or the price on the day of release. Keep in mind that app bundles cannot be made available for pre-order and cannot include apps that are available for pre-order. Apps that are offered for pre-order will not be made available in new app bundles.
Select Make available for pre-order, choose a date to release your app for download, then click Save in the upper-right corner. The release date must be at least two days in the future, but no more than days in the future. Making your app available for pre-order removes other Version Release options from the platform version information page.
Once your app is approved and you're ready to make it available for pre-order, return to Pricing and Availability. Confirm the date your app will be released for download, and click Release as Pre-Order in the upper-right corner. You may edit the release date during the pre-order period, but it must be within days from when the app was first available for pre-order on the App Store.
While your app is available for pre-order, you have the option to release your app to customers immediately. Your app will be released to the App Store. Customers who pre-ordered your app will be notified and your app will automatically download to their device. For more information, see remove an app from the App Store.
If you remove your pre-order offer from the App Store, customers who already pre-ordered your app will not receive the app and will not be charged unless you make it available for pre-order again before the release date. Additionally, once the release date passes, you will no longer be able to re-publish your app as a pre-order. If you have a Paid Applications agreement , you can schedule price changes for your app over time.
You can schedule pricing changes that have a definite start and end date, as well as permanent pricing changes that have no end. For example, you can set a promotional price for a month then return to the regular price. For apps that offer in-app purchases , you can also schedule pricing changes for the in-app purchases.
For more information, see Set in-app purchase pricing or Manage pricing for auto-renewable subscriptions. To schedule price changes, you must have an app that has been submitted for review. You can schedule one or more price changes.
On the right, the Price Schedule appears showing the price, start date, and end date for each price change. The default start date is the current date, and the default end date is No End Date meaning the price remains the same indefinitely. You can select the regions where you want your app to be available on the App Store.
Your app will appear on the App Store in the updated or changed countries or regions within 24 hours. You must set a price for your app before you can edit countries or regions. In the dialog that appears, select the countries or regions you want to make your app available in. Select specific countries or regions: Select the checkbox next to the countries or regions you want to include and deselect the checkbox next to the countries or regions you want to exclude. Add new App Store countries or regions automatically: In the upper-left corner, select the New Countries or Regions checkbox.
Set the category that best describes each app at the app level, which will apply to all in-app purchases. You can also individually manage each in-app purchase — see Set tax category for in-app purchases. Changes to your app's tax category will affect future transactions. If you choose not to make any changes, your apps and in-app purchases will be assigned the App Store software category. You can make adjustments to these settings at any time as the characterization of your app or in-app purchases change or as tax legislation changes.
Selecting categories or attributes that are not appropriate for your app or in-app purchases violates your obligations under the Apple Developer Program License Agreement, the Paid Agreements, and local tax laws. Your tax category selections may result in changes to your proceeds, as proceeds are calculated based on the price of your app or in-app purchase, minus any applicable taxes.
To view your estimated proceeds at each price tier, click All Prices and Currencies from Pricing and Availability. Compare categories to see which best describes your app. For guidance on setting the appropriate tax category, consult your tax advisor.
If the primary purpose of your app is not described by any of the categories below, keep your tax category set to App Store software. Apps that sell digital artwork, including original or manipulated graphics, fonts, and images. If your app provides tools to create or edit artwork, keep your tax category set to "App Store software. Apps that allow users to listen to audio versions of books.
If your app contains episodic series of audio content, select the "Music and other audio" category. Apps that sell electronic versions of printed books, or digital-only content that is published once, under a single title. For content published regularly, consider the "Magazines and other periodicals" category, or the "News publications" category. Apps that facilitate forming new interpersonal relationships by means of text, voice, photo, or video sharing.
Apps that provide on-demand or live streaming of fitness classes. For other apps focused on healthy living, select the "App Store software" category. Apps that create and send electronic versions of a decorative card to express good wishes for an occasion. Apps that deliver content using an issue-based strategy or are producing interactive versions of a printed periodical. If your app contains news content, consider the selecting the "News publications" category.
Apps that are for listening to audio content, including music, podcasts, meditations, radio, and ringtones. Apps that provide information about current events with regular content updates. May be a digital-first, or interactive version of a printed newspaper.
If your app focuses on content about one sector, consider the "Magazines and other periodicals" category. Apps that stream video content. May be accessed through a subscription, pay-per-view, or purchase for permanent consumption. The first full month after you have configured your settings, you can view the Transaction Tax Report - coming soon in Payments and Financial Reports, which shows transaction taxes sales tax, use tax, value-added tax, goods and services tax, and other similar taxes applied to your sales.
Required role: Admin or App Manager. These apps will run natively and use the same frameworks, resources, and runtime environment as they do on iOS and iPadOS. All existing users for the iOS app will be updated to the macOS app. This is set at the app level and will apply to all versions of your app. Apple automatically chooses the minimum macOS version required for compatibility, but you can select a different version when editing availability on an individual app basis.
Select the checkbox if you want the app to be available on the Mac App Store. You can change the minimum macOS version required for compatibility in the drop-down menu. In the dialog that appears, deselect the iPhone and iPad apps you do not want to make available on the Mac App Store.
After your app has been verified, this option will no longer be available in App Store Connect. Note: At the bottom of the Compatibility with Apple Silicon Mac section, it's indicated whether your current and upcoming app versions launch on Apple silicon Macs. Public: Your app will be publicly available on the App Store in the territories you selected and available to anyone for volume purchase through Apple Business Manager or Apple School Manager.
Note: Once your app is approved, the distribution method cannot be changed. All apps listed on the App Store are automatically available for volume purchase for the same price in Apple Business Manager and Apple School Manager, which is where businesses and educational institutions download apps for volume distribution.
This includes the ability to distribute proprietary apps for internal use within your organization. You can specify one or more organizations that can see and download the app in Apple Business Manager or Apple School Manager. You can use in-app purchases to sell a variety of content within your app, including subscriptions, services, and additional features.
You can also promote your in-app purchases directly on the App Store, increasing discoverability for content previously only found inside your app. Users can browse in-app purchases directly on the App Store and start a purchase even before downloading your app. Before releasing your app on the App Store, use TestFlight to distribute your beta apps and app updates to testers for valuable feedback. Enter testing information and invite testers in App Store Connect by adding their names and email addresses or by sharing a public invitation link.
Later, you can make improvements to your app with periodic app updates. After you publish your app on the App Store, you can respond to customer reviews, distribute promo codes, bundle multiple apps in a single purchase, transfer your app to another organization, and more. You can gain insights into the performance of your app by viewing App Analytics data, Sales and Trends reports, and monthly financial reports in Payments and Financial Reports.
View in English. Contact us Support. User accounts and roles overview Add and edit users Change user app access Role permissions Create a sandbox tester account Managing agreements, tax, and banking information To sell apps on the App Store, the Account Holder needs to sign the Paid Applications Agreement in Agreements, Tax, and Banking.
App Store Connect gives you the flexibility to use your iPhone or iPad to manage apps you've developed for the App Store. View app statuses, manage. Read reviews, compare customer ratings, see screenshots, and learn more about Con Edison. Download Con Edison and enjoy it on your iPhone, iPad, and iPod touch. Hello,. my app has an iOS and a tvOS app in App Store Connect. Sadly, I don't have the resources anymore to maintain the tvOS app.