> 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

## Build Detail

The **Build Detail** view provides comprehensive information about native builds for iOS, Android, and Huawei. This information is particularly useful during the distribution process to stores.

<figure><img src="/files/CbKH8ZhKGBQZHI74U4NE" alt=""><figcaption></figcaption></figure>

### Meta Info

Each element in the colored boxes is explained below, grouped under corresponding headings:

<figure><img src="/files/W7w0oDs4iyMFI1ZJUfhV" alt=""><figcaption></figcaption></figure>

<mark style="color:red;">**My Ecommerce App**</mark>\
Displays the name of the project.

<mark style="color:blue;">**Build ID**</mark>\
A unique identifier for the build within the App Maker Platform.

<mark style="color:purple;">**Build Info**</mark>\
Shows the target platform (iOS, Android, or Huawei) and the user who triggered the build.

<mark style="color:orange;">**View All Builds**</mark>\
A quick link that navigates you to the full list of builds for this project.

<mark style="color:green;">**UPDATE STORE STATUS**</mark>\
Clicking this button opens a modal where you can update the store status for successful builds.

<figure><img src="/files/TyrxwiyOVDw2epYq58ER" alt=""><figcaption></figcaption></figure>

* **Store Status:** The **store status** of a build determines what kind of operations can be performed on the platform. The available statuses include:
  * **Approved:** Indicates that the build is live and available to users in the respective store. On the App Maker Platform, this build is marked as the active version for its platform (iOS, Android, or Huawei).

    Additionally, an approved build becomes eligible for [CodePush](/tutorials/app-maker/operate-and-update/codepush.md) deployment—unless it is marked as a **Force Update**.
  * **Pending:** Refers to a build that has been submitted to the store and is currently under review.
  * **Rejected:** Indicates that the build was rejected during the review process. This status must be manually set within the platform.

### Build

The **Build** section provides a breakdown of the core properties associated with a specific build:

<table><thead><tr><th width="147.515625">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Target</strong></td><td>The build process is executed in the specified environment.</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>Env Version</strong></td><td>This version represents the basic edition of your application development platform released by the App Maker team.</td></tr><tr><td><strong>Store Version</strong></td><td>Specifies the version of the app published in the store.</td></tr><tr><td><strong>Store Status</strong></td><td>Represents the app's publication status in the store.</td></tr><tr><td><strong>Created Date</strong></td><td>Specifies the start date.</td></tr></tbody></table>

### Details

The **Details** section 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>Specify the build duration in minutes.</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>Represents the name of the project to which the build is connected.</td></tr><tr><td><strong>Force Update</strong></td><td>Represents whether a "Force update" has been performed. If true, it indicates that the update has been completed.</td></tr><tr><td><strong>Version Code</strong></td><td>In Android and Huawei platforms, the "<strong>Version Code</strong>" value represents the <a href="https://developer.android.com/studio/publish/versioning#versioningsettings">version number</a>.</td></tr></tbody></table>

### **Downloads**

For each successful build, the following downloadable assets are available:

**Build Files**

* For Android and Huawei: APK and AAB formats
* For iOS: IPA format

**Debug Files**

Platform-specific debug symbols can also be downloaded from the additional downloads (⋮) menu to help symbolicate crashes and de-obfuscate stack traces:

* For Android: the ProGuard/R8 **mapping** file and the native **NDK symbols**
* For iOS: the **dSYM** symbols
* Provided as `.zip` archives, available only for successful builds and only when the corresponding file was produced during the build
* Like other build artifacts, debug files are retained for 60 days; after that they can no longer be downloaded

**Log Files**

* Available for both successful and failed builds
* Not supported for builds in other statuses

Some error messages are also visible directly on the build detail screen without downloading the log file.


---

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