> 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
| Column | Description |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **OS** | The platform icon — iOS, Android, or Huawei. |
| **Target** | **Production** or **Staging**. |
| **Tag** | The git tag the build was created from, with a copy icon. |
| **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, with a small status glyph showing whether it's been submitted to (and published on) the store. |
| **Created By** | The user who triggered the build. |
| **Created Date** | When the build was created. Sortable, and sorted newest-first by default. |
| **Duration** | How long the build took, once it has started. |
| **Status** | **Pending**, **Deploying**, **Success**, **Failed**, or **Canceled** — with a queue-position indicator for pending builds waiting on a build agent. |
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](/tutorials/app-maker/projects/project-details.md) via the Latest Builds card's **View Builds** button, or directly at a project's `/deps` URL.
## Columns
| Column | Description |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **OS** | The platform icon — iOS, Android, or Huawei. |
| **Target** | **Production** or **Staging**. |
| **Tag** | The git tag the build was created from, with a copy icon. |
| **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, with a small status glyph showing whether it's been submitted to (and published on) the store. |
| **Created By** | The user who triggered the build. |
| **Created Date** | When the build was created. Sortable, and sorted newest-first by default. |
| **Duration** | How long the build took, once it has started. |
| **Status** | **Pending**, **Deploying**, **Success**, **Failed**, or **Canceled** — with a queue-position indicator for pending builds waiting on a build agent. |
To start a new build, use the **+ New Build** button — see [Create a Build](/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](/tutorials/app-maker/build-and-distribute/build-detail.md) page.
* **Hover a row** for a quick-look popover: status (with a log-download link for failed builds), description, artifact size, platform-specific build info (bundle number/Xcode version for iOS, version code/Java version for Android and Huawei), start/completion times, and Debug Files status (see [Build Detail](/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**.
## 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](/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 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.akinon.com/tutorials/app-maker/build-and-distribute/build-list.md?ask=&goal=
```
`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.
