Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Doc change: Fix description of certificate matching requirement for app updates." into froyo

Browse Source
This commit is contained in:
Dirk Dougherty
2010-06-22 11:13:48 -07:00
committed by Android (Google) Code Review
parent 30cf330fae a767076f46
commit 17ae646586
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/html/guide/publishing/app-signing.jd
View File

@@ -123,13 +123,14 @@ 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> lifespan of your applications. There are several reasons why you should do so: </p>
<ul> <ul>
<li>Application upgrade &ndash; As you release upgrades to your <li>Application upgrade &ndash; As you release updates to your application, you
application, you will want to sign the upgrades with the same certificate, if you will want to continue to sign the updates with the same certificate or set of
want users to upgrade seamlessly to the new version. When the system is certificates, if you want users to upgrade seamlessly to the new version. When
installing an update to an application, if any of the certificates in the the system is installing an update to an application, it compares the
new version match any of the certificates in the old version, then the certificate(s) in the new version with those in the existing version. If the
system allows the update. If you sign the version without using a matching certificates match exactly, including both the certificate data and order, then
certificate, you will also need to assign a different package name to the 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 &mdash; in this case, the user installs the new version as a application &mdash; in this case, the user installs the new version as a
completely new application. </li> completely new application. </li>