> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/learn/features/app-force-update.md).

# App Force Update

App force update feature

> App force updates when a new version of the app is available in the play store. This feature is available from release `v1.5.7` and above.

1. `isAppForceUpdateEnabled` flag set to true in the `POST /schools/login` API response will enable this feature.
2. If the play store has a new version of the app , then in app there would an alert which shows user an alert message to force update the app.
3. If there is any error occurred while populating alert message of app force update, support logs which will capture failure logs.
4. Multiple users on the same device , data will be retained after the update. If there is no data struture change between versions of the app , data stored in the device before update can be pushed to backend after app upgrade.

```javascript

{
    "name": "Dummy school 1",
    "schoolId": "u001",
    "password": "tarento@123",
    "state": "up",
    "autoSync": false,
    "autoSyncFrequency": 600000,
    "storeTrainingData": true,
    "tags": true,
    "supportEmail": "abc@gmail.com , xyz@gmail.com",
    "offlineMode": true,
    "isAppForceUpdateEnabled": true

  }
```

![appForceUpdate](https://user-images.githubusercontent.com/86999055/203745089-11a24f18-69f6-4f22-805a-35439de93ed0.jpg)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://saral.sunbird.org/learn/features/app-force-update.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.