> 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-detail.md).

# Build Detail

<table><thead><tr><th width="147.515625">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>The build's current status (e.g., Pending, Deploying, Success, Failed).</td></tr><tr><td><strong>Target</strong></td><td>The build process is executed in the specified environment (e.g., Production, Staging).</td></tr><tr><td><strong>OS</strong></td><td>The target platform: iOS, Android, or Huawei.</td></tr><tr><td><strong>Type</strong></td><td>The kind of deployment this record represents (Build, for this page).</td></tr><tr><td><strong>Tag</strong></td><td>The Git tag you define when pushing your project to a managed repository.</td></tr><tr><td><strong>Environment</strong></td><td>The App Maker platform edition this build was created on.</td></tr><tr><td><strong>Store</strong></td><td>The version of the app published in the store.</td></tr><tr><td><strong>Version Code / Bundle Number</strong></td><td>On Android and Huawei, the <a href="https://developer.android.com/studio/publish/versioning#versioningsettings">version code</a>; on iOS, the bundle number.</td></tr><tr><td><strong>Upload Duration</strong></td><td>How long it took to upload the build artifact to the store.</td></tr><tr><td><strong>Java Version / Xcode Version</strong></td><td>The Java version used for Android/Huawei builds, or the Xcode version used for iOS builds.</td></tr><tr><td><strong>Artifact Size</strong></td><td>The size of the build artifact (APK/AAB or IPA).</td></tr><tr><td><strong>Store Status</strong></td><td>The app's publication status in the store. See <a href="#store-status-values">Store Status values</a> below.</td></tr><tr><td><strong>Debug Files</strong></td><td>Shows which debug artifacts (Mapping, NDK, Symbols) were uploaded for this build — a check mark means it's available to download; a crossed-out icon means it wasn't produced for this build.</td></tr></tbody></table>

<table><thead><tr><th width="144.32421875">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Duration</strong></td><td>The total build duration.</td></tr><tr><td><strong>Description</strong></td><td>Notes entered during the initialization of the build are displayed here.</td></tr><tr><td><strong>Project</strong></td><td>The name of the project this build is connected to.</td></tr><tr><td><strong>Force Update</strong></td><td>Whether a Force Update has been performed for this build.</td></tr><tr><td><strong>Created Date</strong></td><td>When the build was created.</td></tr><tr><td><strong>Started at</strong></td><td>When the build started running, once available.</td></tr><tr><td><strong>Completed at</strong></td><td>When the build finished, once available.</td></tr></tbody></table>

The **Build Detail** page provides comprehensive information about a native build for iOS, Android, or Huawei — its pipeline progress, its core properties, and its downloadable artifacts. This information is particularly useful during the distribution process to stores.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FeO05Bd69vmiCVgm2pVyH%2Fimage.png?alt=media&amp;token=6028094c-7d6e-448e-9f6a-b6c7f1ca464f" alt=""><figcaption></figcaption></figure>

## Header

At the top of the page you'll find:

* **Project name and "Build Detail"** — the project this build belongs to.
* **View All Builds** — a link back to the full list of builds for this project.
* **Build ID** — the build's unique identifier within the App Maker Platform.
* **Build Info** — the target platform (iOS, Android, or Huawei) and the user who triggered the build.
* **+ CODEPUSH** — opens the form to publish a new [CodePush](/tutorials/app-maker/operate-and-update/codepush.md) update based on this build. Only available once the build has succeeded.

## Pipeline

The **Pipeline** card shows a step-by-step timeline of the build process, with each step's duration and timestamp (e.g., Initializing Pre-build, Verifying Identity, Building, Signing APK/AAB, Exporting, Completed). The step currently running is highlighted, and the connecting line between steps reflects the outcome — green once a step succeeds, red if a step fails, gray for steps still pending, and purple for steps skipped because the build was canceled.

## Build

The **Build** card's header is colored to match the build's status and shows the build's short ID (e.g., `#17467`). The card lists the build's core properties:

<table><thead><tr><th width="147.515625">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>The build's current status (e.g., Pending, Deploying, Success, Failed).</td></tr><tr><td><strong>Target</strong></td><td>The build process is executed in the specified environment (e.g., Production, Staging).</td></tr><tr><td><strong>OS</strong></td><td>The target platform: iOS, Android, or Huawei.</td></tr><tr><td><strong>Type</strong></td><td>The kind of deployment this record represents (Build, for this page).</td></tr><tr><td><strong>Tag</strong></td><td>The Git tag you define when pushing your project to a managed repository.</td></tr><tr><td><strong>Environment</strong></td><td>The App Maker platform edition this build was created on.</td></tr><tr><td><strong>Store</strong></td><td>The version of the app published in the store.</td></tr><tr><td><strong>Version Code / Bundle Number</strong></td><td>On Android and Huawei, the <a href="https://developer.android.com/studio/publish/versioning#versioningsettings">version code</a>; on iOS, the bundle number.</td></tr><tr><td><strong>Java Version / Xcode Version</strong></td><td>The Java version used for Android/Huawei builds, or the Xcode version used for iOS builds.</td></tr><tr><td><strong>Store Status</strong></td><td>The app's publication status in the store. See <a href="#store-status-values">Store Status values</a> below.</td></tr><tr><td><strong>Debug Files</strong></td><td>Shows which debug artifacts (Mapping, NDK, Symbols) were uploaded for this build — a check mark means it's available to download; a crossed-out icon means it wasn't produced for this build.</td></tr></tbody></table>

#### Downloads

At the bottom of the Build card, download the build's artifacts directly:

* **AAB** / **APK** (Android and Huawei) or **IPA** (iOS) — the installable build file. Once its size is known, the button label shows it in parentheses (e.g., `AAB (66.9 MB)`).
* **⋮ (more)** — opens a menu with the remaining downloads: the build **Logs**, and the debug files that were produced for this build (**Mapping** and **NDK Symbols** on Android/Huawei, or the dSYM on iOS).

Downloads are only available for successful builds, and only for files that were actually produced during the build. Like other build artifacts, they are retained for 60 days; after that they can no longer be downloaded.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FGWQNVroCHZP8AwPjot0J%2Fimage.png?alt=media&amp;token=25c6a51a-0df5-4d13-8c90-6e507d0f4ba9" alt=""><figcaption></figcaption></figure>

#### Store Status values

* **Approved** — the build is live and available to users in the store. On the App Maker Platform, this build is marked as the active version for its platform — unless it's marked as a **Force Update**, an approved build also becomes eligible for [CodePush](/tutorials/app-maker/operate-and-update/codepush.md).
* **Pending** — the build has been submitted to the store and is currently under review.
* **Rejected** — the build was rejected during the review process. This status must be manually set within the platform.

## Details

The **Details** card contains supplementary metadata about the build:

<table><thead><tr><th width="144.32421875">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Duration</strong></td><td>The total build duration.</td></tr><tr><td><strong>Description</strong></td><td>Notes entered during the initialization of the build are displayed here.</td></tr><tr><td><strong>Project</strong></td><td>The name of the project this build is connected to.</td></tr><tr><td><strong>Force Update</strong></td><td>Whether a Force Update has been performed for this build.</td></tr><tr><td><strong>Created Date</strong></td><td>When the build was created.</td></tr><tr><td><strong>Started at</strong></td><td>When the build started running, once available.</td></tr><tr><td><strong>Completed at</strong></td><td>When the build finished, once available.</td></tr></tbody></table>

If this build has a CodePush update that's live on the store, a **View Codepush** link also appears here — it shows an animated indicator whenever that CodePush is actively deploying.

Once the build succeeds, this card also shows the store upload action for its platform (e.g., **Upload to Google Play** for Android, or the App Store equivalent for iOS) — see [Distribute to Stores](/tutorials/app-maker/build-and-distribute/distribute-to-stores.md).


---

# 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-detail.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.