Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Yes. Applications which were "installed" (run at least once) before the certificate rollover will continue working on their current phone with no intervention. The only exception is if an application is being run from an SD Card, and the SD card is removed. 

Q. How

...

Upon opening CommCare, a mobile user would see the message: "Certificate invalid according to phone's date."

Q. How do I update an application to be signed against a new certificate?

On CommCare HQ, applications are signed each time a new build version is made. If you make a new build after the certificate has entered service, it will be signed with the new certificate. If no other changes have been made you should simply be able to install "over" the original applicaiton, retaining the installed files. .

Q. How will I know if my CommCare mobile users are having a problem with their certificate?

Upon opening CommCare, a mobile user would see the message: "Certificate invalid according to phone's date."

Q. Is there any way to install an old version if I really need to?


Yes. If the phone gives you the error "Certificate invalid according to phone's date" you when you try to run CommCare, you can still run that version. There are two workarounds for running a version of CommCare which has an expired certificate. 

...

Q. Do I need to update which version of CommCare my applicaiton is built against (IE: CommCare 2.3.0 to CommCare 2.8.0) in order to get the new certificate?

No. The application is signed after the build, and CommCare retains the binary for all of the versions which have been built against, so you can make a new build of your app with its current CommCare version, regardless of which version of CommCare you are running. However, we do recommend that you consider updating CommCare if you are getting a new certificate in order to take advantage of new bug fixes and features available on newer versions of CommCare.

...