> For the complete documentation index, see [llms.txt](https://assetstore.essentialkit.voxelbusters.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://assetstore.essentialkit.voxelbusters.com/features/app-updater/playmaker/use-cases/use-case-1-request-update-info-and-prompt.md).

# Request Update Info And Prompt (End-to-end)

## Goal

Check App Store/Play Store for newer app version and prompt user to update if available.

This use-case intentionally combines:

* the “check” part (UseCase2)
* the “prompt” part (UseCase3)

If you only need one side of the flow, use those focused use-cases instead.

## Actions Required

| Action                                      | Purpose                                    |
| ------------------------------------------- | ------------------------------------------ |
| AppUpdaterRequestUpdateInfo                 | Query store for update status (cached)     |
| AppUpdaterGetRequestUpdateInfoSuccessResult | Read updateStatus after SUCCESS            |
| AppUpdaterPromptUpdate                      | Show native update prompt/flow             |
| AppUpdaterGetRequestUpdateInfoError         | Read error after FAILURE (optional)        |
| AppUpdaterGetPromptUpdateError              | Read error after prompt FAILURE (optional) |

## Variables Needed

* updateStatus (Enum: AppUpdaterUpdateStatus)
* isForceUpdate (Bool) (your policy)

## Implementation Steps

### 1. RequestUpdateInfo (Entry State)

**Action:** AppUpdaterRequestUpdateInfo

* **Events:**
  * successEvent → GetStatus
  * failureEvent → (Optional) ReadRequestError

### 2. GetStatus

**Action:** AppUpdaterGetRequestUpdateInfoSuccessResult

* **Outputs:**
  * updateStatus → updateStatus

### 3. EvaluateStatus

* If updateStatus == Available or Downloaded → PromptUpdate
* Else → ContinueNormal

### 4. PromptUpdate

**Action:** AppUpdaterPromptUpdate

* **Inputs:**
  * isForceUpdate: isForceUpdate
  * promptTitle / promptMessage: optional
* **Events:**
  * successEvent → ContinueNormal
  * failureEvent → (Optional) ReadPromptError
  * progressUpdateEvent → (Optional) UpdateUIProgress (Android only)

### 5. (Optional) ReadRequestError / ReadPromptError

* Use **AppUpdaterGetRequestUpdateInfoError** / **AppUpdaterGetPromptUpdateError** to read `errorCode` + `errorDescription`.

### 6. ContinueNormal

Proceed to main app experience

## Common Issues

* **Network dependency**: Requires internet connection
* **Store caching**: Version info may lag actual deployment
* **Frequency**: Check on app launch, not mid-session
* **User experience**: Don't spam update prompts

## Platform Behavior

* **iOS**: Opens App Store app page
* **Android**: Opens Google Play Store app page

## Use When

* App launch (cold start only)
* After resuming from background (optional)
* Critical security patches
* Breaking backend API changes


---

# 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://assetstore.essentialkit.voxelbusters.com/features/app-updater/playmaker/use-cases/use-case-1-request-update-info-and-prompt.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.