Update notification
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
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.
For example:
Current version: 1.1
New version: 1.2
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.
Check the Current Code Version:
Head over to the 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.
For example:
If the current version is 1.1, the new version should be 1.2 or higher.
Submit the Updated Build:
Publish the updated version on the app stores ( and ).
Verify Update Notifications:
Once users update to the new version with the correct code version, they will no longer receive unnecessary update notifications.
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.