Merge "Doc change: Remove refs to Copy Protection and note EOL in GP." into jb-mr1-dev

<h2 id="licensing">Protecting your App</h2>

<p>To help you protect your application against piracy, Google Play offers a

licensing service that you can implement in your app. It’s a network-based

service that lets an application query a trusted Google Play licensing server to

determine whether the application is licensed to the current device user.</p>

<p>Google Play provides two key features to help you protect your application

against piracy &mdash; Google Play Licensing and app encryption.</p>

<p> Google Play Licensing is a network-based service that you implement in your

app. The service lets your app query a trusted licensing server at runtime, to

determine whether the app is licensed to the current device user. You can use

the licensing service to protect any app, even apps that you distribute for

free. For an overview of the service, see <a

href="{@docRoot}google/play/licensing/index.html">Application

Licensing</a>.</p>

<p>Additionally, Google Play offers app encryption to help protect your priced

apps. When delivering your priced apps to devices running Android 4.1 or higher,

Google encrypts the app binary so that it can be run only by the user who

downloaded it, on the device to which it was originally downloaded. Your priced

apps benefit from app encryption automatically — there's no extra

development work or configuration needed.</p>

  </tr>

  <tr>

    <td>{@code productId}</td>

    <td>The item's product identifier. Every item has a product ID, which you must specify in the application's product list on the Google Play publisher site.</td>

    <td>The item's product identifier. Every item has a product ID, which you must specify in the application's product list on the Google Play Developer Console.</td>

  </tr>

  <tr>

    <td>{@code purchaseTime}</td>

</div>

</div>

<p>The Google Play publisher site provides several tools that help you test your In-app Billing

<p>The Google Play Developer Console provides several tools that help you test your In-app Billing

implementation before it is published. You can use these tools to create test accounts and purchase

special reserved items that send static billing responses to your application.</p>

<p>You do not need to list the reserved products in your application's product list. Google Play

already knows about the reserved product IDs. Also, you do not need to upload your application to

the publisher site to perform static response tests with the reserved product IDs. You can simply

the Developer Console to perform static response tests with the reserved product IDs. You can simply

install your application on a device, log into the device, and make billing requests using the

reserved product IDs.</p>

testing.</p>

<p>To test your In-app Billing implementation with actual in-app purchases, you will need to

register at least one test account on the Google Play publisher site. You cannot use your

register at least one test account on the Google Play Developer Console. You cannot use your

developer account to test the complete in-app purchase process because Google Checkout does not let

you buy items from yourself. If you have not set up test accounts before, see <a

href="{@docRoot}google/play/billing/billing_admin.html#billing-testing-setup">Setting up test

<p>To test your In-app Billing implementation with actual purchases, follow these steps:</p>

<ol>

  <li><strong>Upload your application as a draft application to the publisher site.</strong>

  <li><strong>Upload your application as a draft application to the Developer Console.</strong>

    <p>You do not need to publish your application to perform end-to-end testing with real product

    IDs; you only need to upload your application as a draft application. However, you must sign

    your application with your release key before you upload it as a draft application. Also, the

<h3>Uploading the sample application</h3>

<p>After you build a release version of the sample application and sign it, you need to upload it as

a draft to the Google Play publisher site. You also need to create a product list for the in-app

a draft to the Google Play Developer Console. You also need to create a product list for the in-app

items that are available for purchase in the sample application. The following instructions show you

how to do this.</p>

<ol>

 <li><strong>Make one of your test accounts the primary account on your device.</strong>

    <p>The primary account on your device must be one of the <a

    href="{@docRoot}google/play/billing/billing_admin.html#billing-testing-setup">test accounts</a>

    that you registered on the Google Play publisher site. If the primary account on your device is not a

    that you registered on the Google Play Developer Console. If the primary account on your device is not a

    test account, you must do a factory reset of the device and then sign in with one of your test

    accounts. To perform a factory reset, do the following:</p>

    <ol>

<p>To help ensure the integrity of the transaction information that is sent to your application,

Google Play signs the JSON string that is contained in the <code>PURCHASE_STATE_CHANGED</code>

broadcast intent. Google Play uses the private key that is associated with your publisher account

to create this signature. The publisher site generates an RSA key pair for each publisher account.

to create this signature. The Developer Console generates an RSA key pair for each publisher account.

You can find the public key portion of this key pair on your account's profile page. It is the same

public key that is used with Google Play licensing.</p>

  <td>Required for <code>REQUEST_PURCHASE</code> requests.</td>

  <td>The product ID of the item you are making a billing request for. Every in-app item that you

  sell using Google Play's In-app Billing service must have a unique product ID, which you

  specify on the Google Play publisher site.</td>

  specify on the Google Play Developer Console.</td>

</tr>

<tr>

  <td><code>NONCE</code></td>

<tr>

  <td>productId</td>

  <td>The item's product identifier. Every item has a product ID, which you must specify in the

  application's product list on the Google Play publisher site.</td>

  application's product list on the Google Play Developer Console.</td>

</tr>

<tr>

  <td>purchaseTime</td>