> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/build-list.md).

# Build List

The **Builds** list is the full, filterable history of every native build ever created for a project — every iOS, Android, and Huawei build, across both Production and Staging targets. Open it from a project's [Dashboard](https://docs.akinon.com/tutorials/app-maker/projects/project-details.md) via the Latest Builds card's **View Builds** button, or directly at a project's `/deps` URL.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FIdWZy3ZqpufIAoz0igOx%2Fbuild-and-distribute-build-list-build-list.png?alt=media" alt="Builds list for a project, showing OS, Build, Environment, Store, Created By, Created and Status columns"><figcaption></figcaption></figure>

## Columns

| Column          | Description                                                                                                                                                                                                                                                                                                |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **OS**          | The platform icon — iOS, Android, or Huawei.                                                                                                                                                                                                                                                               |
| **Build**       | The build's identity in one cell: the full git tag the build was created from, with a copy icon. Underneath, in muted text, are the build number and the target (**Production** or **Staging**), for example `#17467 · Production`, and a **Live** badge when this is the platform's currently live build. |
| **Environment** | The build's runtime (environment) version. A lock icon appears next to it if the build has been force-updated.                                                                                                                                                                                             |
| **Store**       | The build's store version, followed by a status label: **Pending**, **Live**, **Approved**, or **Rejected**. A build that has a store version but has not reached the store (it is still running, failed, or was canceled) shows a grey **N/A**; a build with no store version shows only a dash.          |
| **Created By**  | The user who triggered the build.                                                                                                                                                                                                                                                                          |
| **Created**     | When the build was created, with how long the build ran underneath once it has started. Sortable, and sorted newest-first by default.                                                                                                                                                                      |
| **Status**      | **Pending**, **Deploying**, **Success**, **Failed**, or **Canceled** — with a queue-position indicator for pending builds waiting on a build agent.                                                                                                                                                        |

There is no separate Target column. To narrow the list to Production or Staging builds, use the **Target** filter below.

To start a new build, use the **+ New Build** button — see [Create a Build](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/create-a-build.md) for the full flow.

## Filters

Use the filter icon to open the filter panel:

* **OS** — iOS, Android, or Huawei.
* **Target** — Production or Staging.
* **Live** — whether the build is the platform's currently live build.
* **Store Status** — the build's submission status on the store.
* **Force Update** — whether the build has been force-updated.
* **Environment Version** / **Store Version** — free-text match.
* **Created By** — a specific user (only shown if you have permission to view organization users).
* **Created Date** — a specific date.
* **Status** — Success, Deploying, Pending, Failed, or Canceled.

Active filters appear as removable chips above the list; clear them individually or all at once.

## Row Details

* **Click a row** to open its [Build Detail](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/build-detail.md) page.
* **Hover a row** for a quick-look popover. Its header shows the tag and build number. Status, Description and Artifact rows are left out when there is nothing to show; any other row without a value shows a dash:

  * **Status** — shown for a build that has not succeeded, with a log-download link for a failed build and the queue position for a pending one.
  * **Description**, if the build has one.
  * **Store** — the store version with the same **Pending**, **Live**, **Approved** or **Rejected** label as the list.
  * **Artifact** — for a successful build, what it produced with its size: **IPA** on iOS, **APK** and **AAB** on Android and Huawei, for example `APK 49.46 MB · AAB 31.20 MB`.
  * Platform-specific build info: bundle number and Xcode version on iOS, version code and Java version on Android and Huawei.
  * **Started At** and **Completed At**.
  * **Debug Files**, for a successful build — see [Build Detail](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/build-detail.md) for what each Debug Files state means.

  The popover also offers **View Details** and, once the build has shipped to the store, **View Code Push**. For a build that **failed or was canceled** it also offers **+ Run New**, which starts a new build with the same settings. A successful or still-running build does not offer it. Starting a run from the list keeps you on the list: it reloads and the new build appears as a Pending row. See [Run a Finished Build Again](https://docs.akinon.com/tutorials/app-maker/build-and-distribute/create-a-build.md#run-a-finished-build-again).
* **Download an artifact from the popover.** While an artifact can be downloaded, its entry on the **Artifact** row is a link with a download icon: click it to download that file. Only the artifacts the build can actually deliver are offered, so an older build may offer an AAB even though only one generic size is listed. Once a build's retention period has passed, its entries turn grey with a clock icon, and hovering one explains that the artifact has expired and can no longer be downloaded.

## Bulk Force Update

Select up to five eligible builds using the row checkboxes — a build is selectable only once it has succeeded, been published to the store, is not already the live build, and hasn't already been force-updated — then choose **Force Update** from the **Select Action** dropdown and **Apply** to force-update all of them at once. See [Force Update](https://docs.akinon.com/tutorials/app-maker/operate-and-update/force-update.md) for what force-updating a build does.

A build whose own CodePush is still queued or rolling out shows that status glyph in place of its checkbox — it isn't a Force Update target while its CodePush is in flight. The same glyph appears next to **View Code Push** in the row's hover popover.

## Auto-Refresh

The list polls automatically every 10 seconds while any build is **Pending** or **Deploying**, so a build's status updates without a manual reload. Polling stops once nothing is in progress.


---

# 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.akinon.com/tutorials/app-maker/build-and-distribute/build-list.md?ask=<question>&goal=<user_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.
