> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/app-publication/publishing-your-app/ios-publication-complete-process/app-store-publication.md). # 6. App Store publication ## App Store Publication This guide will explain how to fill the App required information in the [App Store Connect](https://appstoreconnect.apple.com) and submit the app for review. {% hint style="info" %} It's important that you check the [App store guidelines](https://docs.bravostudio.app/app-publication/publishing-your-app/publication-rejection-from-the-app-stores) to avoid rejections by Apple. {% endhint %} ### Version Information To start you need to upload at least the [screenshots](https://help.apple.com/app-store-connect/#/devd274dd925) for iPhone 5.5'' and 6.5'' screens, be sure to check or [Bravo Stores Assets Kit](https://www.figma.com/community/file/832996906819389496) to generate your screenshots easily. Here are the specific sizes required: * At lease three screenshots for 6.5" display (1242x2688px) * At lease three screenshots for 5.5'' display (1242 x 2208px) ![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MhO5TFJVak3JV9H96v3%2F-MhO5hneG0_ZyqM-LOur%2FScreenshot_2020-10-26_at_14.28_1_\(1\).png?generation=1629287538526511\&alt=media) Then it is required to fill in the app information: * Promotion Text (optional) * Description * Keywords (al least one) * Support URL * Marketing URL (optional) * Build (select version) * Copyright * Age rating * Contact Information * Advertising Identifier → **NO** If you get asked if your app uses Encryption or the app uses the **Advertisement Identifier (IDFA)**, answer **NO**, as Bravo doesn't use any of those. Regarding encryption, Bravo uses the https protocol that is exempt. ### App Information ![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MhO5TFJVak3JV9H96v3%2F-MhO5hndCV5195vpfuZo%2FGroup_6.png?generation=1629287538574694\&alt=media) Then it is required to fill in the app information: * Name * Subtitle * Privacy Policy URL * Primary Language * Category On **Pricing and availability**, we can select the desired **price tier** or if the app will be **free**, also the availability in the different app store countries. ### App privacy Regarding the **App Privacy** section, now is mandatory to be filled in, you will need to answer a questionnaire regarding the tracking that is done in the app. Bravo apps do track data from the apps using some third party providers, we do collect some identifiers to allow some of the functionalities like a **DeviceID** and **UserID** (for **App functionality**) which can be used on the API Bridge, we do track some anonymous usage data on the apps which helps us improving our product and resolving issues (**usage data for analytics**). And finally we also **collect crash data, performance data and diagnostic data for app functionality** to make our apps better. Here would be the final result after filling all the information. ![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MhO5TFJVak3JV9H96v3%2F-MhO5hnfTI4k6zXu_e7K%2FScreenshot_2021-05-11_at_12.45.27.png?generation=1629287538593533\&alt=media) Once everything is filled in,add the bundle package via the Transporter app, locate the build you uploaded, and you're ready to submit for review. Click on the `Submit for Review` **button to send for publication review** 🚀. At this point, your app will be reviewed by Apple and can be accepted or denied. The first time an app is submitted it can take up to 6-8 days to be reviewed. Updates use to take a few hours. If your app gets rejected, read carefully the reasons Apple point out, fix them and re-submit. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bravostudio.app/app-publication/publishing-your-app/ios-publication-complete-process/app-store-publication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.