| Info | ||
|---|---|---|
| ||
is approaching What do I need to do? Some commonly asked questions are answered below, followed by technical details about application signing |
...
On CommCare HQ, applications are signed each time a new version is made. If you make a new build version after the certificate has entered service (September 26, 2013), it will be signed with the new certificate.
...
Workaround
1- Change the phone's time
(recommended)- On the phone, go to the settings menu, and configure the phone's date and time settings. Set the date to be inside before the validity period for the certificate used to sign the binary you are running (from the table above)certificate expired.
- Run CommCare at least once, being sure to set any of the necessary application access permissions beforehand
- Return to the settings menu and set the phone's date and time to the correct value
Q. Do I need to update which version of CommCare my
...
application is built
...
with (IE: CommCare 2.3.0 to CommCare 2.8.0) in order to get the new certificate?
No. The application is signed after the buildversion is created, and CommCare retains the binary for all of the prior 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.
...
Service Entry | Certificate Valid From | Certificate Expiration Date | Status |
|---|---|---|---|
| November 2, 2009 | November 13, 2010 | Expired |
| September 21, 2010 | November 13, 2011 | Expired |
November 14, 2011 | September 13, 2011 | November 12, 2013 | Valid (retired)Expired |
| September 26, 2013 | September 24, 2011 | November 12, 2015 | Valid |
...