> For the complete documentation index, see [llms.txt](https://onestore-dev.gitbook.io/dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onestore-dev.gitbook.io/dev/cht/docs/apps/android/review-history.md).

# Review History

## **Overview**

This page allows developers to request and review the review status and results of the submitted app binary.

Developers can monitor the review process and check whether the binary has been approved.

## Review History

<figure><img src="/files/7A7tbKY9jPiSNv2TfOPt" alt=""><figcaption></figcaption></figure>

### **Requested**

The date and time when the developer requested binary review.

### **Result Date**

The date and time when the review was completed.

### **Review Result**

* Once review is completed, the result for the binary will be displayed.
* **Approved**: The review was successfully completed, and the binary is approved.
* **Approved(Recommendations of revision)**: The review is completed, but modifications are required.
* **Rejected**: The review request has been rejected.

### **Content information**

* **Binary Information**
  * Details about the submitted binary.
* **Review Report**
  * A detailed report on the review result, including reasons for approval, modification recommendations, or rejection.
* **Download Review Report**
  * Once review is completed, developers can download the review report to review **detailed feedback**.
  * If the result is **"Approved(Recommendations of revision)"** or **"Rejected"**, developers must refer to the review report for necessary modifications.


---

# 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://onestore-dev.gitbook.io/dev/cht/docs/apps/android/review-history.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.