diff options
author | 2010-06-22 11:25:59 -0700 | |
---|---|---|
committer | 2010-06-22 11:25:59 -0700 | |
commit | ca36e9eebe252e04dbadeb07282c1eba8d9f080b (patch) | |
tree | 1121ab3e9c81f7abca7063a732de35acef1500bf | |
parent | 57b5326561b6edb22b09016985b41b7cdb2156c0 (diff) | |
parent | 7c1a2dfa8930fd12bb8791fc02bace751917bdee (diff) |
am 7c1a2dfa: am 17ae6465: Merge "Doc change: Fix description of certificate matching requirement for app updates." into froyo
Merge commit '7c1a2dfa8930fd12bb8791fc02bace751917bdee' into gingerbread-plus-aosp
* commit '7c1a2dfa8930fd12bb8791fc02bace751917bdee':
Doc change: Fix description of certificate matching requirement for app updates.
-rw-r--r-- | docs/html/guide/publishing/app-signing.jd | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/html/guide/publishing/app-signing.jd b/docs/html/guide/publishing/app-signing.jd index 8c37d7a02f12..34d9419193c6 100644 --- a/docs/html/guide/publishing/app-signing.jd +++ b/docs/html/guide/publishing/app-signing.jd @@ -123,14 +123,15 @@ all of your applications with the same certificate, throughout the expected lifespan of your applications. There are several reasons why you should do so: </p> <ul> -<li>Application upgrade – As you release upgrades to your -application, you will want to sign the upgrades with the same certificate, if you -want users to upgrade seamlessly to the new version. When the system is -installing an update to an application, if any of the certificates in the -new version match any of the certificates in the old version, then the -system allows the update. If you sign the version without using a matching -certificate, you will also need to assign a different package name to the -application — in this case, the user installs the new version as a +<li>Application upgrade – As you release updates to your application, you +will want to continue to sign the updates with the same certificate or set of +certificates, if you want users to upgrade seamlessly to the new version. When +the system is installing an update to an application, it compares the +certificate(s) in the new version with those in the existing version. If the +certificates match exactly, including both the certificate data and order, then +the system allows the update. If you sign the new version without using matching +certificates, you will also need to assign a different package name to the +application — in this case, the user installs the new version as a completely new application. </li> <li>Application modularity – The Android system allows applications that |