> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/notifications/update-notification.md).

# Update notification

### Why are my app users receiving update notifications if they have already updated to the new app version? 

If your app users are receiving update notifications even after updating to the latest version, it is likely due to an issue with the code versioning of your app build. This article explains why this happens and how to resolve it.

#### **What Causes This Issue?**

When you launch a new version of your app on app stores, the build version of the app must have an incremental code version compared to the previous version.

{% hint style="success" %}
For example:

* Current version: 1.1
* New version: 1.2
  {% endhint %}

If the new version is published with a decremental or non-incremental code version (e.g., 1.0 or 1.1), the app will continue to notify users to update to the newer version, even if they are already using it. This happens because the app stores identify the app version as outdated based on the incorrect code versioning.

#### **How to Resolve This Issue?**

* Check the Current Code Version:
  * Head over to the [**download section**](https://app.appmysite.com/app/download) of the app concerned and verify the current code version of your app build.
* Publish a New Version with an Incremented Code Version:
  * Update your app to a new version with an incremented code version.

{% hint style="success" %}
For example:

* If the current version is 1.1, the new version should be 1.2 or higher.
  {% endhint %}

* Submit the Updated Build:
  * Publish the updated version on the app stores ([**Google Play**](/app/upload/android/submit-new-android-version.md) & [**Apple App Store**](/app/upload/ios/submit-new-ios-version.md)).

* Verify Update Notifications:
  * Once users update to the new version with the correct code version, they will no longer receive unnecessary update notifications.

{% hint style="danger" %}
Preventing this issue in the future

* Follow standard versioning practices (e.g., 1.0 → 1.1 → 1.2) to avoid conflicts.
* Double-check the code version number during the build submission process.
  {% endhint %}


---

# 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://docs.appmysite.com/frequently-asked-questions/notifications/update-notification.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.