From 9c1f71966ea9ece22cd60a021b95ecc68261da07 Mon Sep 17 00:00:00 2001 From: quddusc Date: Thu, 2 Jan 2014 11:39:02 -0800 Subject: docs: Updated instructions for setting up In-app Billing test accounts to reflect new dev console UI. Bug: 7044477 Change-Id: I722dc2e47c8dbe0cba48e44434d62fe28f23714f --- docs/html/google/play/billing/billing_admin.jd | 41 +++++++++++++----------- docs/html/google/play/billing/billing_testing.jd | 4 +-- 2 files changed, 25 insertions(+), 20 deletions(-) diff --git a/docs/html/google/play/billing/billing_admin.jd b/docs/html/google/play/billing/billing_admin.jd index f1e4ec434d4c..dd29b82b2205 100644 --- a/docs/html/google/play/billing/billing_admin.jd +++ b/docs/html/google/play/billing/billing_admin.jd @@ -97,8 +97,8 @@ number of in-app items.

  1. Log in to your publisher account.
    2. -
  2. In the All Google Play listings panel, under the application name, click - In-app Products.
    3. +
  3. In the All Applications panel, click on the + app name, then select In-app Products.
  4. Click Add new product (see figure 2) and provide details about the item you are selling and then click Save or Publish.
@@ -363,10 +363,11 @@ with the locale field.

  1. Log in to your publisher account.
    2. -
  2. In the All Google Play listings panel, under the application name, click - In-app Products.
    3. -
  3. On the In-app Products List page, click Choose File and select your CSV -file. +
  4. In the All Applications panel, click on the app + name, then select In-app Products.
    5. +
  5. On the In-app Products List page, click Import/Export + > Import in-app products from CSV file, then select your + CSV file.

    The CSV file must be on your local computer or on a local disk that is connected to your computer.

    6. @@ -377,7 +378,6 @@ file. Overwriting does not delete items that are on a product list but not present in the CSV file.

    -
  6. On the In-app Products List page, click Import from CSV.

You can also export an existing product list to a CSV file by clicking Export to CSV @@ -471,9 +471,8 @@ accounts yourself and distribute the credentials to your developers or testers.<

  1. Log in to your publisher account.
    2. -
  2. Click the Settings icon. (If you are using the old Developer Console UI, click - Edit profile in the upper left part of the page, under your name,)
    3. -
  3. Locate the License Testing panel. (In the old UI, scroll down to the Licensing & In-app Billing panel.)
    4. +
  4. Click the Settings icon.
    5. +
  5. Locate the License Testing panel.
  6. Add the email addresses for the test accounts you want to register, separating each account with a comma.
  7. Click Save to save your profile changes.
    8. @@ -481,18 +480,24 @@ accounts yourself and distribute the credentials to your developers or testers.<

    Getting an app's license key

    -

    The Google Play Developer Console provides a public licensing key for each app. To get the key for an app, -load the app's publishing details in the Developer Console and click the Settings icon. The key -for the app is available for copy/paste in License Key for this Application field, as shown in the figure below.

    - -

    Previously, the Developer Console provided a single public key per developer account. To transition apps to the -new per-app public key, the Developer Console set the app-specific key as the former developer key. This ensures -compatibility for apps that depend on the (former) developer key.

    +

    The Google Play Developer Console provides a public licensing key for each +app. To get the key for an app, follow these steps:

    +
      +
    1. Open the All Applications panel.
      2. +
    2. Click on the app name, then select Services & APIs.
      3. +
    3. Scroll down to the Your License Key for this Application +field to locate the key for the app, as shown in the figure below.
      4. +
    +

    Previously, the Developer Console provided a single public key per developer +account. To transition apps to the new per-app public key, the Developer Console +set the app-specific key as the former developer key. This ensures compatibility +for apps that depend on the (former) developer key.

    - Figure 4. You can find the license key for each app in the Services & APIs panel. + Figure 4. You can find the license key for each app in the + Services & APIs panel.

    diff --git a/docs/html/google/play/billing/billing_testing.jd b/docs/html/google/play/billing/billing_testing.jd index 42b6d65e288a..9d1964a268e7 100644 --- a/docs/html/google/play/billing/billing_testing.jd +++ b/docs/html/google/play/billing/billing_testing.jd @@ -82,10 +82,10 @@ 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.

    -

    Next, create license test accounts for authorized users. In the Developer +

    Next, create license test accounts for authorized users. In the Developer Console, go to Settings > Account details, then in the License Testing section, add the addresses to Gmail accounts -with testing status. For more information, see field. For more information, see Setting Up for Test Purchases.

    Once you’ve added the users as license tester accounts and saved the change, -- cgit v1.2.3-59-g8ed1b