am 38bb601e: am 305f3e21: am 79d3b623: am b9c5af3a: Merge "docs: Removed...

</p>

</div>

<p>You can create a product list for any published application or any draft application that's been

<p>You can create a product list for any published application, or any

application in the alpha or beta channels, that's been

uploaded and saved to the Developer Console. However, you must have a Google Wallet merchant

account and the application's manifest must include the <code>com.android.vending.BILLING</code>

permission. If an application's manifest does not include this permission, you will be able to edit

<a href="{@docRoot}google/play/billing/billing_integrate.html#billing-permission">Updating Your

Application's Manifest</a>.</p>

<p class="note"><strong>Note:</strong> Previously you could test an app by

uploading an unpublished "draft" version. This functionality is no longer

supported; instead, you must publish it to the alpha or beta distribution

channel. For more information, see <a

href="{@docRoot}google/play/billing/billing_testing.html#draft_apps">Draft Apps

are No Longer Supported</a>.

<p>In addition, an application package can have only one product list. If you create a product

list for an application, and you use the <a

href="{@docRoot}google/play/publishing/multiple-apks.html">multiple APK feature</a> to distribute

  <h2>In this document</h2>

  <ol>

    <li><a href="#testing-purchases">Testing In-app Purchases</a></li>

        <li><a href="#billing-testing-static">Testing with static responses</a></li>

    <li><a href="#billing-testing-static">Testing with Static Responses</a></li>

    <li><a href="#billing-testing-real">Setting Up for Test Purchases</a></li>

    <li><a href="#draft_apps">Draft Apps are No Longer Supported</a></li>

  </ol>

  <h2>See also</h2>

  <ol>

<p>First, upload and publish in-app products that you want testers to be able to

purchase. You can upload and publish in-app products in the Developer Console. 

Note that you can upload and publish your in-app items before you publish the

APK itself. For example, you can publish your in-app items while your APK is

still a draft. </p>

APK itself.</p>

<p>Next, create license test accounts for authorized users. In the Developer

Console, go to <strong>Settings</strong> &gt; <strong>Account details</strong>,

only be able to make test purchases. </p>

<h2 id="billing-testing-static">Testing with static responses</h2>

<h2 id="billing-testing-static">Testing with Static Responses</h2>

<p>We recommend that you first test your In-app Billing implementation using static responses from

Google Play. This enables you to verify that your application is handling the primary Google

Play responses correctly and that your application is able to verify signatures correctly.</p>

Play responses correctly and that your application is able to verify signatures correctly. You can do this

even if the app hasn't been published yet.</p>

<p>To test your implementation with static responses, you make an In-app Billing request using a

special item that has a reserved product ID. Each reserved product ID returns a specific static

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

reserved product IDs.</p>

<p class="note"><strong>Note:</strong> Previously you could test an app by

uploading an unpublished "draft" version. This functionality is no longer

supported. However, you can test your app with static responses even before you

upload it to the Google Play store. For more information, see <a

href="#draft_apps">Draft Apps are No Longer Supported</a>.

<p>There are four reserved product IDs for testing static In-app Billing responses:</p>

<ul>

  </li>

</ul>

<p>In some cases, the reserved items may return signed static responses, which lets you test

signature verification in your application. To test signature verification with the special reserved

product IDs, you may need to set up <a

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

upload your application as a unpublished draft application. Table 1 shows you the conditions under

which static responses are signed.</p>

<p class="table-caption" id="static-responses-table"><strong>Table 1.</strong>

Conditions under which static responses are signed.</p>

<table>

<tr>

<th>Application ever been published?</th>

<th>Draft application uploaded and unpublished?</th>

<th>User who is running the application</th>

<th>Static response signature</th>

</tr>

<tr>

<td>No</td>

<td>No</td>

<td>Any</td>

<td>Unsigned</td>

</tr>

<tr>

<td>No</td>

<td>No</td>

<td>Developer</td>

<td>Signed</td>

</tr>

<tr>

<td>Yes</td>

<td>No</td>

<td>Any</td>

<td>Unsigned</td>

</tr>

<tr>

<td>Yes</td>

<td>No</td>

<td>Developer</td>

<td>Signed</td>

</tr>

<tr>

<td>Yes</td>

<td>No</td>

<td>Test account</td>

<td>Signed</td>

</tr>

<tr>

<td>Yes</td>

<td>Yes</td>

<td>Any</td>

<td>Signed</td>

</tr>

</table>

<p>In some cases, the reserved items may return signed static responses, which

lets you test signature verification in your application. The reserved items

only return signed responses if the user running the application has a <a

href="{@docRoot}distribute/googleplay/start.html">developer</a> or <a

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

account.</a>

<p>To make an In-app Billing request with a reserved product ID, you simply construct a normal

<code>REQUEST_PURCHASE</code> request, but instead of using a real product ID from your

experience, including the actual purchases from Google Play and the actual checkout flow that

users will experience in your application.</p>

<p class="note"><strong>Note</strong>: You do not need to publish your application to do end-to-end

testing. You only need to upload your application as a draft application to perform end-to-end

testing.</p>

<p class="note"><strong>Note:</strong> You can do end-to-end testing of your app

  by publishing it to an <a

  href="{@docRoot}distribute/googleplay/developer-console.html#alpha-beta">alpha

  distribution channel</a>. This allows you to publish the app to the Google

  Play store, but limit its availability to just the testers you designate. </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 Developer Console. You cannot use your

<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 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

    version number of the uploaded application must match the version number of the application you

    load to your device for testing. To learn how to upload an application to Google Play, see

    <a href="http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113469">Uploading

    applications</a>.</p>

  <li><strong>Upload your application to the <a

  href="{@docRoot}distribute/googleplay/developer-console.html#alpha-beta">alpha

  distribution channel</a> with the Developer Console.</strong>

   <p class="note"><strong>Note:</strong> Previously you could test an app by

    uploading an unpublished "draft" version. This functionality is no longer

    supported; instead, you must publish it to the alpha or beta distribution

    channel. For more information, see <a href="#draft_apps">Draft Apps are No

    Longer Supported</a>.

  </li>

  <li><strong>Add items to the application's product list.</strong>

    <p>Make sure that you publish the items (the application can remain unpublished). See <a

href="{@docRoot}distribute/tools/launch-checklist.html">publishing on Google Play</a>.

</p>

<h2 id="draft_apps">Draft Apps are No Longer Supported</h2>

<p>Previously, you could publish a "draft" version of your app for testing. This

functionality is no longer supported. Instead, there are two ways you can test

how a pre-release app functions on the Google Play store:</p>

<ul>

  <li>You can publish an app to the <a

  href="{@docRoot}distribute/googleplay/developer-console.html#alpha-beta">alpha

  or beta distribution channels</a>. This makes the app available on the Google

  Play store, but only to the testers you put on a "whitelist".</li>

  <li>In a few cases, you can test Google Play functionality with an unpublished

  app. For example, you can test an unpublished app's in-app billing support by

  using <a

  href="{@docRoot}google/play/billing/billing_testing.html#billing-testing-static">static

  responses</a>, special reserved product IDs that always return a specific

  result (like "purchased" or "refunded").</li>

</ul>

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>

<p class="caution"><strong>Caution:</strong> Draft applications are no longer

supported. To test an application, publish it in the <a

href="{@docRoot}distribute/googleplay/developer-console.html#alpha-beta">alpha

or beta channels</a>. For more information, see <a

href="{@docRoot}google/play/billing/billing_testing.html#draft_apps">Draft Apps

are No Longer Supported</a>.</p>

<ol>

  <li><strong>Upload the release version of the sample application to Google Play.</strong>

    <p>Do not publish the sample application; leave it as an unpublished draft application. The

  // Intent actions that we receive in the BillingReceiver from Google Play.

  // These are defined by Google Play and cannot be changed.

  // The sample application defines these in the Consts.java file.

  public static final String ACTION_NOTIFY = "com.android.vending.billing.IN_APP_NOTIFY";

  public static final String ACTION_RESPONSE_CODE = "com.android.vending.billing.RESPONSE_CODE";

  public static final String ACTION_NOTIFY =

      "com.android.vending.billing.IN_APP_NOTIFY";

  public static final String ACTION_RESPONSE_CODE =

      "com.android.vending.billing.RESPONSE_CODE";

  public static final String ACTION_PURCHASE_STATE_CHANGED =

      "com.android.vending.billing.PURCHASE_STATE_CHANGED";

      Log.w(TAG, "unexpected action: " + action);

    }

  }

  // Perform other processing here, such as forwarding intent messages to your local service.

  // Perform other processing here, such as forwarding intent messages

  // to your local service.

}

</pre>

    <!-- Required to download files from Google Play -->

    <uses-permission android:name="android.permission.INTERNET" />

    <!-- Required to keep CPU alive while downloading files (NOT to keep screen awake) -->

    <!-- Required to keep CPU alive while downloading files

        (NOT to keep screen awake) -->

    <uses-permission android:name="android.permission.WAKE_LOCK" />

    <!-- Required to poll the state of the network connection and respond to changes -->

    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <!-- Required to poll the state of the network connection

        and respond to changes -->

    <uses-permission

        android:name="android.permission.ACCESS_NETWORK_STATE" />

    <!-- Required to check whether Wi-Fi is enabled -->

    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>

    <!-- Required to read and write the expansion files on shared storage -->

    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

    <uses-permission

        android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

    ...

</manifest>

</pre>

    @Override

    public void onReceive(Context context, Intent intent) {

        try {

            DownloaderClientMarshaller.startDownloadServiceIfRequired(context, intent,

                    SampleDownloaderService.class);

            DownloaderClientMarshaller.startDownloadServiceIfRequired(context,

                intent, SampleDownloaderService.class);

        } catch (NameNotFoundException e) {

            e.printStackTrace();

        }

    <p>For example, the sample app provided in the Apk Expansion package calls the

following method in the activity's {@link android.app.Activity#onCreate onCreate()} method to check

whether the expansion files already exist on the device:</p>

<pre>

boolean expansionFilesDelivered() {

    for (XAPKFile xf : xAPKS) {

        String fileName = Helpers.getExpansionAPKFileName(this, xf.mIsBase, xf.mFileVersion);

        String fileName = Helpers.getExpansionAPKFileName(this, xf.mIsBase,

            xf.mFileVersion);

        if (!Helpers.doesFileExist(this, fileName, xf.mFileSize, false))

            return false;

    }

    return true;

}

</pre>

    <p>In this case, each {@code XAPKFile} object holds the version number and file size of a known

expansion file and a boolean as to whether it's the main expansion file. (See the sample

application's {@code SampleDownloaderActivity} class for details.)</p>

display the download progress (see the next step). If the response <em>is</em> {@code

NO_DOWNLOAD_REQUIRED}, then the files are available and your application can start.</p>

    <p>For example:</p>

<pre>

@Override

public void onCreate(Bundle savedInstanceState) {

                notifierIntent, PendingIntent.FLAG_UPDATE_CURRENT);

        // Start the download service (if required)

        int startResult = DownloaderClientMarshaller.startDownloadServiceIfRequired(this,

        int startResult =

            DownloaderClientMarshaller.startDownloadServiceIfRequired(this,

                        pendingIntent, SampleDownloaderService.class);

        // If download has started, initialize this activity to show download progress

        // If download has started, initialize this activity to show

        // download progress

        if (startResult != DownloaderClientMarshaller.NO_DOWNLOAD_REQUIRED) {

            // This is where you do set up to display the download progress (next step)

            // This is where you do set up to display the download

            // progress (next step)

            ...

            return;

        } // If the download wasn't necessary, fall through to start the app

    startApp(); // Expansion files are available, start the app

}

</pre>

  </li>

  <li>When the {@code startDownloadServiceIfRequired()} method returns anything <em>other

than</em> {@code NO_DOWNLOAD_REQUIRED}, create an instance of {@code IStub} by

starts the download. </p>

    <p>For example, in the previous code sample for {@link android.app.Activity#onCreate

onCreate()}, you can respond to the {@code startDownloadServiceIfRequired()} result like this:</p>

<pre>

        // Start the download service (if required)

        int startResult = DownloaderClientMarshaller.startDownloadServiceIfRequired(this,

        int startResult =

            DownloaderClientMarshaller.startDownloadServiceIfRequired(this,

                        pendingIntent, SampleDownloaderService.class);

        // If download has started, initialize activity to show progress

        if (startResult != DownloaderClientMarshaller.NO_DOWNLOAD_REQUIRED) {

expansion files. You might want to provide a user preference to enable downloads over

the cellular network. In which case, you can call:

<pre>

mRemoteService.setDownloadFlags(IDownloaderService.FLAGS_DOWNLOAD_OVER_CELLULAR);

mRemoteService

    .setDownloadFlags(IDownloaderService.FLAGS_DOWNLOAD_OVER_CELLULAR);

</pre>

</dd>

</dl>

// The shared path to all app expansion files

private final static String EXP_PATH = "/Android/obb/";

static String[] getAPKExpansionFiles(Context ctx, int mainVersion, int patchVersion) {

static String[] getAPKExpansionFiles(Context ctx, int mainVersion,

      int patchVersion) {

    String packageName = ctx.getPackageName();

    Vector<String> ret = new Vector<String>();

    if (Environment.getExternalStorageState().equals(Environment.MEDIA_MOUNTED)) {

    if (Environment.getExternalStorageState()

          .equals(Environment.MEDIA_MOUNTED)) {

        // Build the full path to the app's expansion files

        File root = Environment.getExternalStorageDirectory();

        File expPath = new File(root.toString() + EXP_PATH + packageName);

<pre>

// Get a ZipResourceFile representing a merger of both the main and patch files

ZipResourceFile expansionFile = APKExpansionSupport.getAPKExpansionZipFile(appContext,

ZipResourceFile expansionFile =

    APKExpansionSupport.getAPKExpansionZipFile(appContext,

        mainVersion, patchVersion);

// Get an input stream for a known file inside the expansion file ZIPs

opens, it's important that you test this process to be sure your application can successfully query

for the URLs, download the files, and save them to the device.</p>

<p>To test your application's implementation of the manual download procedure, you must upload

your application to Google Play as a "draft" to make your expansion files available for

download:</p>

<ol>

  <li>Upload your APK and corresponding expansion files using the Google Play Developer

Console.</li>

  <li>Fill in the necessary application details (title, screenshots, etc.). You can come back and

finalize these details before publishing your application.

  <p>Click the <strong>Save</strong> button. <em>Do not click Publish.</em> This saves

the application as a draft, such that your application is not published for Google Play users,

but the expansion files are available for you to test the download process.</p></li>

  <li>Install the application on your test device using the Eclipse tools or <a

href="{@docRoot}tools/help/adb.html">{@code adb}</a>.</li>

  <li>Launch the app.</li>

</ol>

<p>If everything works as expected, your application should begin downloading the expansion

<p>To test your application's implementation of the manual download procedure,

you can publish it to the alpha or beta channel, so it will only be available to

authorized testers.

If everything works as expected, your application should begin downloading the expansion

files as soon as the main activity starts.</p>

<p class="note"><strong>Note:</strong> Previously you could test an app by

uploading an unpublished "draft" version. This functionality is no longer

supported; instead, you must publish it to the alpha or beta distribution

channel. For more information, see <a

href="{@docRoot}google/play/billing/billing_testing.html#draft_apps">Draft Apps

are No Longer Supported</a>.

<h2 id="Updating">Updating Your Application</h2>

<tr>

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

<td>The application is licensed to the user. The user has purchased the

application or the application only exists as a draft.</td>

application, or is authorized to download and install the alpha or beta version

of the application.</td>

<td>Yes</td>

<td><code>VT</code>,&nbsp;<code>GT</code>, <code>GR</code></td>

<td><em>Allow access according to {@code Policy} constraints.</em></td>

href="{@docRoot}google/play/licensing/setting-up.html#test-env">

Setting Up The Testing Environment</a>, the response code can be manually

overridden for the application developer and any registered test users via the

Google Play Developer Console.

<br/><br/>

Additionally, as noted above, applications that are in draft mode (in other

words, applications that have been uploaded but have <em>never</em> been

published) will return {@code LICENSED} for all users, even if not listed as a test

user. Since the application has never been offered for download, it is assumed

that any users running it must have obtained it from an authorized channel for

testing purposes.</p>

Google Play Developer Console.</p>

<p class="note"><strong>Note:</strong> Previously you could test an app by

uploading an unpublished "draft" version. This functionality is no longer

supported; instead, you must publish it to the alpha or beta distribution

channel. For more information, see <a

href="{@docRoot}google/play/billing/billing_testing.html#draft_apps">Draft Apps

are No Longer Supported</a>.

<h2 id="extras">Server Response Extras</h2>

        }

    } else if (mLastResponse == LicenseResponse.RETRY &&

                ts < mLastResponseTime + MILLIS_PER_MINUTE) {

        // Only allow access if we are within the retry period or we haven't used up our

        // max retries.

        // Only allow access if we are within the retry period

        // or we haven't used up our max retries.

        return (ts <= mRetryUntil || mRetryCount <= mMaxRetries);

    }

    return false;