Updating CommCare Content is the process of updating an installed application to a newer version of the application that has been released from CommCareHQ.
There are two components to CommCare:
1- the CommCare software which is the the shell of the program. CommCare mobile client is the same for all projects.
2- the CommCare content which is often referred to as the "application" (forms, case management, multimedia, etc.)
These instructions are for the application content component. For instructions on updating the CommCare software, see this page.
Before deploying changes to your application you may want to read Making Changes to a Deployed Application which outlines how changes can affect data exports or application usability.
Once you have lots of versions they will all be listed as follows:
The main function to be aware of is the Latest Released label. Once an application is marked as "Released" it means that when a mobile worker updates the application on their phone, CommCareHQ will send the most recent released version. You should be able to update your phone without re-installing your application with these steps:
There are several other actions on this page:
When looking for updates, CommCare apps will look at the latest, released build. If an application is already updated to (or was installed with) the newest build which has been marked as "Latest Released", it won't update, even if newer (unreleased) builds have been created. If the latest released build's version is lower than the installed build, an update will not occur. If, for example, the last release was version 70, the currently installed build is version 73 (for testing and development) and there exists a newer unreleased build 74, the app will not attempt to update. If 74 is released, the current build will update the next time it checks.
On CommCare Android you can view the current app version by choosing About CommCare from the settings menu either before or after logging in.
You can also determine the deployed version on CommCareHQ by using the Application Status Report in the Manage Deployment Reports.
CommCare can be configured to check for updates on a regular schedule. This is specified by the Auto Update Frequency setting in the Advanced Settings section of the Application Settings. When set to auto-update, CommCare will attempt to check CommCareHQ for new resources on a daily or weekly schedule. This check occurs in the background, immediately after login. If updates are found, they will be downloaded and applied the next time the user logs in. Users can cancel updates being downloaded by navigating to "Settings -> Update App" on the mobile device.
If the app can't contact the server, it will try again on a future login.
Advanced Feature: Update Target Options: Allows you to turn on Developer Mode and use the Latest Saved State of your app without making a full release.
A manual update can also be initiated from the CommCare mobile application.
Option 1 - Normal Update (Recommended Workflow): This option is the normal update workflow for apps, and is recommended in most scenarios. Your device will need to have a network connection in order to update this way.
Option 2 - Offline Update: This option is primarily useful in scenarios where you know that you will not have a network connection when performing the update. Note that you WILL still need a connection to download the .ccz file initially (step 3 below). This option may also be useful if you want to update to a specific version that is not the latest starred build, or (for advanced users) to update to a .ccz that you have edited locally.
Remote update is not well supported on feature phones; in general you should expext to simply remove the old version of the app and install the new version.
There is a update feature which sometimes works in areas with very good connectivity: Login as "admin" or a user with admin rights, and from the home screen navigate to Settings -> Check for Updates or in the login screen go to Options -> Tools -> Check for Updates
When new features are added they are generally added to Major and Minor updates to CommCare. If an application on HQ is moved to a higher Minor or Major version number (1.2 -> 1.3 for instance), an application's resource files won't be able to be downloaded by an older version of CommCare.
Advanced Software Upgrades
Since CommCare's resources are almost always included with the application files, upgrading CommCare often happens at the same time as the Application Resources are updated, and as such a full re-installation should be used to update both at the same time (see note below). This method of upgrading is not fully supported, but can be used by experts.
In-Place upgrades basically involve installing the applicaiton onto the phone without first removing the old version. This is possible using the OTA, Phone-to-Phone, and Memory Card installation techniques. It is never recommended unless you are using a completely offline deployment, or in specific future use cases where OTA installation is being used to manage remote upgrades.
The below are guidelines for the minimum that should be required when performing an upgrade. Keep in mind that the safest way to upgrade an app is to always follow the full re-installation instructions.
Major Version (1.N.N -> 2.N.N)
Major version bumps will first require the migration of your application's resources to the newest version using CommCare HQ. Once a build of the app is available on the newest version is available, you should follow the full re-installation instructions.
Minor Version (1.1.N -> 1.2.N)
Minor version bumps shouldn't require any changes to your application resources (although they will often permit you to include new features in them), simply create a new build with the existing resources and perform a full re-installation.
Maintenance Version (1.1.1 -> 1.1.2)
Maintenance releases are generally designed to be safe for an in-place upgrade on top of the old app (generally in order to correct bugs with OTA upgrades, although this feature isn't widely usable yet). However, a full re-installation is still recommended.