> For the complete documentation index, see [llms.txt](https://docs.tempokit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tempokit.com/publishing-to-the-app-stores/apple-app-store-publishing/submitting-an-app-for-review-and-publishing-to-the-app-store.md).

# Submitting an App for Review and Publishing to the App Store

Visit <https://appstoreconnect.apple.com/apps>&#x20;

Click on the application and add the details below:

**Add App Details to Product page**

Add app name, icon, description, [screenshots](https://previewed.app?via=tempokit), app previews, and keywords. You can also add a ctachy subtitle and promotional text.&#x20;

[View details on creating a great product page](https://developer.apple.com/app-store/product-page/)

**Build**

Select the build you used for testflight.

#### App Review Information

Create a test user in the app and enter it here.

**App Privacy Details**

Enter your app’s privacy content here.

[Learn about providing app privacy details](https://developer.apple.com/app-store/app-privacy-details/)

**Submission**

Then click submit for review at the bottom of the page!

[View App Store Connect Help for more info](https://help.apple.com/app-store-connect/)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tempokit.com/publishing-to-the-app-stores/apple-app-store-publishing/submitting-an-app-for-review-and-publishing-to-the-app-store.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.