Unable to update custom scoped applications after publishing new version from source instance to App RepoSummaryThis article will touch on why you may not be able to update the latest version of your custom scoped application when accessing My Company Applications after publishing a new version of the app from the source instance to the repo.ReleaseAll ReleasesInstructionsOne of the first things you should look at is the current version of the application on the target instance. If the application has already been previously installed on the target instance, you will be able to find the current version of the application by accessing the Store Applications [sys_store_app] record. Once you have access the Store Application record, take note of what the current version is - you will find this by looking at the Version field. For example, let's say the current version which exists on the target instance is 1.1.9. On the source instance, if you update the latest version of the application to version 1.0.11 to the app repo, this will register the application as an older version to what exists on the target instance because the numbering convention is both different and non-incremental. In order to ensure you can update this application on the target instance, the version of the application on the source instance must be incremented - 1.1.10 - or take on a higher numbering convention like 1.2.0 or 1.3.0