Skip to content

Commit be0dab4

Browse files
Bill GruberAndroid Git Automerger
authored andcommitted
am 69e2484: Merge "Licensing docs: clarifies server response for draft apps Bug 2900690" into ics-mr0
* commit '69e24843fc89dcdd35802dbb6a2b693650ec8a41': Licensing docs: clarifies server response for draft apps Bug 2900690
2 parents 9d3dffc + 69e2484 commit be0dab4

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

docs/html/guide/publishing/licensing.jd

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -100,9 +100,14 @@ application. </p>
100100
<h4>Application, Android Market client, and server</h4>
101101

102102
<p>The licensing service is based on the capability of the Android Market server
103-
to determine whether a given user is licensed to use a given application. The
104-
server considers a user licensed if the user is recorded to have purchased the
105-
application, or if the application is available for free. To properly identify
103+
to determine whether a given user is licensed to use a given application. The licensing server
104+
considers a user to be licensed if the user is a recorded purchaser of an application. If a paid
105+
application has been uploaded to Android Market but saved only as a draft application (in
106+
other words, the app is unpublished), the licensing server considers all users to be licensed users
107+
of the application. Keep in mind, you cannot implement Android Market Licensing in a free
108+
application.</p>
109+
110+
<p>To properly identify
106111
the user and determine the license status, the server requires information about
107112
the application and user &mdash; the application and the Android Market client
108113
work together to assemble the information and pass it to the server. </p>
@@ -243,7 +248,7 @@ application: </p>
243248

244249
<ul>
245250
<li>Only paid applications published through Market can use the
246-
service. </li>
251+
service.</li>
247252
<li>An application can use the service only if the Android Market client is
248253
installed on its host device and the device is running Android 1.5 (API level 3)
249254
or higher.</li>
@@ -258,8 +263,8 @@ practices in this document, you can help ensure that your implementation will be
258263
secure.</li>
259264
<li>Adding licensing to an application does not affect the way the application
260265
functions when run on a device that does not offer Android Market.</li>
261-
<li>Licensing is currently for paid apps only, since free apps are considered
262-
licensed for all users. If your application is already published as free,
266+
<li>Licensing is currently for paid apps only, since draft apps are
267+
licensed for all users. If your application is already published as a free app,
263268
you won't be able to upload a new version that uses licensing.</li>
264269
</ul>
265270

@@ -698,7 +703,7 @@ haven't done that already, do it now before continuing. </p>
698703
<p>Next, open the application's project properties window, as shown below.
699704
Select the "Android" properties group and click <strong>Add</strong>, then
700705
choose the LVL library project (com_android_vending_licensing) and click
701-
<strong>OK</strong>. For more information, see
706+
<strong>OK</strong>. For more information, see
702707
<a href="{@docRoot}guide/developing/projects/projects-eclipse.html#SettingUpLibraryProject">
703708
Managing Projects from Eclipse with ADT</a></p>.
704709

@@ -727,7 +732,7 @@ properties, including the reference to the library project:</p>
727732
--library <em>path/to/my/library_project</em>
728733
</pre>
729734

730-
<p>For more information about working with library projects,
735+
<p>For more information about working with library projects,
731736
see <a href="{@docRoot}guide/developing/projects/projects-cmdline.html#SettingUpLibraryProject">
732737
Managing Projects from the Command Line</a></p>.
733738

@@ -1226,6 +1231,8 @@ whether there is a valid license response cached locally, in
12261231
<li>Otherwise, the LicenseChecker initiates a license check request that is sent
12271232
to the licensing server.</li>
12281233
</ul>
1234+
<p class="note"><strong>Note:</strong> The licensing server always returns
1235+
<code>LICENSED</code> when you perform a license check of a draft application.</p>
12291236
</li>
12301237
<li>When a response is received, LicenseChecker creates a LicenseValidator that
12311238
verifies the signed license data and extracts the fields of the response, then
@@ -1384,7 +1391,7 @@ methods post to the Handler.</li>
13841391
</ol>
13851392

13861393
<p>If you want your LicenseCheckerCallback methods to update the UI thread,
1387-
instantiate a {@link android.os.Handler} in the main Activity's
1394+
instantiate a {@link android.os.Handler} in the main Activity's
13881395
{@link android.app.Activity#onCreate(android.os.Bundle) onCreate()} method,
13891396
as shown below. In this example, the LVL sample application's
13901397
LicenseCheckerCallback methods (see above) call <code>displayResult()</code> to
@@ -2338,7 +2345,7 @@ Policy <code>processServerResonse()</code> method with a "RETRY" response code.
23382345
</p>
23392346

23402347
<p>In general, the RETRY response code is a signal to the application that an
2341-
error has occurred that has prevented a license check from completing.
2348+
error has occurred that has prevented a license check from completing.
23422349

23432350
<p>The Android Market server helps an application to manage licensing under
23442351
error conditions by setting a retry "grace period" and a recommended maximum

0 commit comments

Comments
 (0)