diff options
Diffstat (limited to 'docs/html')
20 files changed, 112 insertions, 121 deletions
diff --git a/docs/html/distribute/googleplay/about/distribution.jd b/docs/html/distribute/googleplay/about/distribution.jd index 746e180..78883b4 100644 --- a/docs/html/distribute/googleplay/about/distribution.jd +++ b/docs/html/distribute/googleplay/about/distribution.jd @@ -24,17 +24,18 @@ the rollout across your customer base, Google Play also lets users accept automatic updates of your app, so that your updates are delivered and installed as soon as you publish them.</p> + <h2 id="targeting">Reaching the customers you want</h2> +<div class="figure-right" style="width:400px;"> +<img src="{@docRoot}images/gp-dc-countries.png" class="frame"> +</div> + <p>Google Play does more than connect your app with users—it helps you reach the broadest possible distribution across the Android ecosystem, while making sure that your app is only available to the audience that you want to reach.</p> -<div style="float:right;margin-left:18px;border:1px solid #DDD;margin:1.5em;"> -<img src="{@docRoot}images/gp-dc-countries.png" style="width:400px;padding:4px;margin-bottom:0;"> -</div> - <h3 id="geotargeting">Geographic targeting</h3> <p>You can use controls in the Google Play Developer Console to easily @@ -47,16 +48,15 @@ your targeted countries before downloading your app. You can change your country and carrier targeting at any time just by saving changes in the Google Play Developer Console.</p> +<div class="figure-right" style="width:400px;"> +<img src="{@docRoot}images/gp-supported-dev-requirements.png" class="frame"> +</div> + <p>To help you market to users around the world, you can <a href="{@docRoot}distribute/googleplay/publish/preparing.html#localize">localize your store listing</a>, including app details and description, promotional graphics, screenshots, and more.</p> -<div style="float:right;margin-left:18px;border:1px solid #DDD;margin:1.5em;"> -<img src="{@docRoot}images/gp-supported-dev-requirements.png" -style="width:400px;padding:4px;margin-bottom:0;"> -</div> - <h3 id="captargeting">Capabilities targeting</h3> <p>Google Play also lets you control distribution according to device features diff --git a/docs/html/distribute/googleplay/about/monetizing.jd b/docs/html/distribute/googleplay/about/monetizing.jd index 8bafd53..8233a31 100644 --- a/docs/html/distribute/googleplay/about/monetizing.jd +++ b/docs/html/distribute/googleplay/about/monetizing.jd @@ -116,8 +116,8 @@ see <a href="{@docRoot}google/play/billing/index.html">Google Play In-app Billin <h2 id="buyer-currency" style="margin-top:1.5em;">Flexible pricing in the currencies of your customers</h2> -<div style="float:right;margin-left:18px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-buyer-currency.png" style="width:240px;padding:4px;margin-bottom:1em;"> +<div class="figure-right" style="width:250px;"> +<img src="{@docRoot}images/gp-buyer-currency.png" class="frame"> </div> <p>Google Play gives you complete control over how you price your products. You diff --git a/docs/html/distribute/googleplay/publish/console.jd b/docs/html/distribute/googleplay/publish/console.jd index cd1fd80..069b2d2 100644 --- a/docs/html/distribute/googleplay/publish/console.jd +++ b/docs/html/distribute/googleplay/publish/console.jd @@ -1,4 +1,4 @@ -page.title=The Developer Console +page.title=Developer Console @jd:body @@ -9,41 +9,40 @@ Developer Console, which will be the home for your app publishing operations and tools on Google Play. This sections below introduce a few of the key areas you'll find in the Developer Console.</p> -<div style="width:610px;margin-left:"> -<div style="width:610px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-dc-home.png" style="width:600px;padding:4px;margin-bottom:0em;"> -</div> -<p class="image-caption" style="padding:.5em"><span -style="font-weight:500;">All applications page</span>: Gives you a quick +<div class="figure" style="width:756px;"> +<img src="{@docRoot}images/gp-dc-home.png" class="frame"> +<p class="img-caption"><strong>All applications page</strong>: Gives you a quick overview of your apps, lets you jump to stats, reviews, and product details, or upload a new app. </p> </div> - -<h3 id="profile">Your Account Details</h3> - -<div style="width:408px;float:right;margin:1.5em;"> -<div style="width:410px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-dc-profile.png" style="width:400px;padding:4px;margin-bottom:0em;"> -</div> -<p class="image-caption" style="padding:.5em"><span -style="font-weight:500;">Account details page</span>: Specifies your developer +<div class="figure-right" style="width:450px;"> +<img src="{@docRoot}images/gp-dc-profile.png" class="frame"> +<p class="img-caption"><strong>Account details page</strong>: Specifies your developer identity and contact information, accounts for app testing, and more.</p> </div> -<p>Your developer profile identifies you to Google Play and to your customers. -During registration you must provide information for your profile, but you can go -back at any time to edit the information and change your settings. </p> +<h3 id="profile">Your account details</h3> + +<p>The account details page is where you specify basic information about yourself +or your company in a developer profile. The information in your developer profile +is important because it identifies you to Google Play and also to your customers.</p> + +<p>During registration you must provide the information for your profile, but you can +go back at any time to edit the information and change your settings. </p> <p>Your developer profile contains:</p> <ul> -<li>Your developer name — the name you want to show users on your product -details page and elsewhere on Google Play. +<li>Your developer name — the name you want to show users on your store +listing page and elsewhere on Google Play. </li> <li>Your developer contact information — how Google can contact you if -needed (this information isn't exposed to users). -<li>Merchant information, in-app billing information.</li> +needed (this information isn't exposed to users).</li> +<li>Your developer website URL — shown to users on your store listing page +so they can learn more about your company or products.</li> </ul> +<p>On the account details page you can also register for a merchant account, set +up test accounts for Google Play licensing, and more. </p> <h3 id="user-accounts">Multiple user accounts</h3> @@ -55,6 +54,13 @@ have access to. For example, an owner can grant users access to publishing and app configuration, but not access to financial reports. </p> +<div class="figure-right" style="width:450px;"> +<img src="{@docRoot}images/gp-dc-details.png" class="frame"> +<p class="img-caption"><strong>Store listing page</strong>: Lets you upload your +graphic assets, description, support information, and other information to +create the store listing page for a specific app.</p> +</div> + <h3 id="merchant">Linking your Merchant Account</h3> <p>If you want to sell apps or in-app products, you can link your Google @@ -62,17 +68,6 @@ Checkout Merchant account to your developer profile. Google Play uses the linked Checkout account for financial and tax identification and monthly payouts of sales. </p> -<div style="width:410px;float:right;margin:1.5em;"> -<div style="width:410px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-dc-details.png" style="width:400px;padding:4px;margin-bottom:0em;"> -</div> -<p class="image-caption" style="padding:.5em"><span -style="font-weight:500;">Store Listing page</span>: Lets you upload your -graphic assets, description, support information, and other information to -create the product details page for a specific app.</p> -</div> - - <h3 id="details">Your store listing details</h3> <p>The Developer Console lets you set up a colorful storefront page for your app @@ -86,15 +81,14 @@ what's great about your app, and you can provide a localized description, add notes about the latest version, and more. You can update your store listing at any time, even if you don’t have a new version of your application.</p> - <h3 id="uploading">Uploading and publishing</h3> <p>From the Developer Console you can quickly upload a release-ready APK and publish it when you're ready. The app is a <em>draft</em> until you publish it, -at which time Google Play makes your store listing and app available to +at which time Google Play makes your store listing page and app available to users. You can unpublish the app at any time.</p> -<h3 id="controls">Distribution Controls</h3> +<h3 id="controls">Distribution controls</h3> <p>In the Developer Console you can manage what countries and territories the app is distributed to and, for some countries, you can choose what carriers you @@ -103,8 +97,7 @@ want to target.</p> <p>You can also see the list of devices that your app is currently available to, based on any distribution rules declared in its manifest file.</p> - -<h3 id="profile">Selling and pricing your Products</h3> +<h3 id="selling">Selling and pricing your products</h3> <p>The Developer Console gives you tools to set prices for your apps and in-app products. Your app can either be free to download or priced (charged before @@ -149,17 +142,18 @@ time, just by saving changes in the Developer Console.</p> <a href="{@docRoot}google/play/billing/index.html">In-app Billing</span></a> developer documentation.</p></div></div> -<p><a href="{@docRoot}google/play/billing/index.html">In-app Billing</a> is a Google Play service that lets you monetize your apps in more ways by selling in-app products and subscriptions. In-app products are one-time purchases, while subscriptions are recurring charges on an monthly or annual basis.</p> +<p><a href="{@docRoot}google/play/billing/index.html">In-app Billing</a> is +a Google Play service that lets you monetize your apps in more ways by selling +in-app products and subscriptions. In-app products are one-time purchases, while +subscriptions are recurring charges on an monthly or annual basis.</p> <p>From the Developer Console you can create product lists for in-app products and subscriptions, set prices, and publish.</p> -<div style="width:410px;float:right;margin:1.5em;"> -<div style="width:410px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-dc-reviews.png" style="width:400px;padding:4px;margin-bottom:0em;"> -</div> -<p class="image-caption" style="padding:.5em"><span style="font-weight:500;">User -reviews page</span>: Gives you access to user reviews for a specific app. +<div class="figure-right" style="width:410px;"> +<img src="{@docRoot}images/gp-dc-reviews.png" class="frame"> +<p class="img-caption"><strong>User +reviews page</strong>: Gives you access to user reviews for a specific app. You can filter reviews in a number of ways to locate issues more easily and support your customers more effectively.</p> </div> @@ -182,7 +176,7 @@ performance of your app. </p> <p>You can view installations of your app measured by unique users, as well as by unique devices. For user installations, you can view active installs, total -installs, daily installs and uninstalls, and metrics about the user reviews. +installs, daily installs and uninstalls, and metrics about user ratings. For devices, you can see active installs as well as daily installs, uninstalls, and upgrades.</p> @@ -197,12 +191,8 @@ other factors. You can even focus in on data inside a dimension by adding specific points (such as individual platform versions or languages) to the timeline.</p> -<div style="width:610px;margin:1.5em;margin-left:0"> -<div style="width:610px;border:1px solid #DDD;"> -<img src="{@docRoot}images/gp-dc-stats.png" -style="width:600px;padding:4px;margin-bottom:0em;"> -</div> -<p class="image-caption" style="padding:.5em"><span style="font-weight:500;">App -statistics page</span>: Shows you a variety of statistics about a -specific app's installation performance over time.</p> +<div style="width:530px;"> +<img src="{@docRoot}images/gp-dc-stats.png" class="frame"> +<p class="img-caption"><strong>App statistics page</strong>: Shows you a variety +of statistics about a specific app's installation performance over time.</p> </div> diff --git a/docs/html/distribute/googleplay/publish/preparing.jd b/docs/html/distribute/googleplay/publish/preparing.jd index 406d412..0925f3c 100644 --- a/docs/html/distribute/googleplay/publish/preparing.jd +++ b/docs/html/distribute/googleplay/publish/preparing.jd @@ -422,8 +422,8 @@ and add it to a localized version of the promotional graphic.</p> started on creating them and localizing them well in advance of your target publishing date. </p> -<p class="note"><strong>Note:</strong> Localized promotional graphics and videos are supported -only in the new Developer Console design.</p> +<p class="note"><strong>Note:</strong> Localized promotional graphics and videos +are supported only in the new Developer Console design.</p> <table> <tr> @@ -547,7 +547,7 @@ and reviews, or any other channel available.</p> <h2 id="final-checks">16. Final checks and publishing</h2> <p>When you think you are ready to publish, sign in to the Developer Console and take a few moments for a few -final checks:</p> +final checks.</p> <p>Make sure that: </p> diff --git a/docs/html/google/play/billing/billing_admin.jd b/docs/html/google/play/billing/billing_admin.jd index cfa7a30..91883da1 100644 --- a/docs/html/google/play/billing/billing_admin.jd +++ b/docs/html/google/play/billing/billing_admin.jd @@ -492,7 +492,7 @@ compatibility for apps that depend on the (former) developer key. </p> <div style="margin:1em;"> <img style="border:1px solid #ddd;padding-bottom:.5em" src="{@docRoot}images/in-app-billing/billing_app_key.png" xheight="510" id="figure4" /> <p class="img-caption" style="padding-left:.5em;"> - <strong>Figure 4.</strong> You can find the license key for each app in the <strong>Services & APIs</strong> panel. + <strong>Figure 4.</strong> You can find the license key for each app in the <strong>Services & APIs</strong> panel. </p> </div> diff --git a/docs/html/google/play/billing/v2/billing_integrate.jd b/docs/html/google/play/billing/v2/billing_integrate.jd index 7b748a3..f2846f0 100755 --- a/docs/html/google/play/billing/v2/billing_integrate.jd +++ b/docs/html/google/play/billing/v2/billing_integrate.jd @@ -170,15 +170,14 @@ your project</a>.</p> following:</p> <ol> - <li><strong>Add your Google Play public key to the sample application code.</strong> + <li><strong>Add your app's public key to the sample application code.</strong> <p>This enables the application to verify the signature of the transaction information that is returned from Google Play. To add your public key to the sample application code, do the following:</p> <ol> - <li>Log in to your Google Play <a href="http://play.google.com/apps/publish">publisher - account</a>.</li> - <li>On the upper left part of the page, under your name, click <strong>Edit - Profile</strong>.</li> + <li>Log in to your Google Play <a href="http://play.google.com/apps/publish">Developer + console</a>.</li> + <li>On the upper left part of the page, All Applications, click the application name.</strong>.</li> <li>On the Edit Profile page, scroll down to the <strong>Licensing & In-app Billing</strong> panel.</li> <li>Copy your public key.</li> @@ -1044,14 +1043,14 @@ obfuscate your code.</p> <p>You will need to use your Google Play public key to perform the signature verification. The following procedure shows you how to retrieve Base64-encoded public key from the Google Play -publisher site.</p> +Developer Console.</p> <ol> <li>Log in to your <a href="http://play.google.com/apps/publish">publisher account</a>.</li> - <li>On the upper left part of the page, under your name, click <strong>Edit profile</strong>.</li> - <li>On the Edit Profile page, scroll down to the Licensing & In-app Billing panel (see figure - 2).</li> - <li>Copy your public key.</li> + <li>On the upper left part of the page, click <strong>All applications</strong> and then click + the app name in the listing.</li> + <li>Click <em>Services & APIs</em> and find "Your License Key for this Application" on the page. </li> + <li>Copy the app's public key.</li> </ol> <p class="caution"><strong>Important</strong>: To keep your public key safe from malicious users and @@ -1060,11 +1059,13 @@ runtime from pieces or use bit manipulation (for example, XOR with some other st actual key. The key itself is not secret information, but you do not want to make it easy for a hacker or malicious user to replace the public key with another key.</p> -<img src="{@docRoot}images/billing_public_key.png" height="510" id="figure2" /> -<p class="img-caption"> - <strong>Figure 2.</strong> The Licensing and In-app Billing panel of your account's Edit Profile - page lets you see your public key. -</p> +<div style="width:640px;"> +<img src="{@docRoot}images/licensing_public_key.png" class="frame"> +<p class="img-caption"><strong>Figure +2.</strong> An app's license key is available from the Services & APIs page in +the Developer Console.</p> +</div> + <h2 id="billing-implement">Modifying Your Application Code</h2> diff --git a/docs/html/google/play/licensing/setting-up.jd b/docs/html/google/play/licensing/setting-up.jd index 1d4e775..d83f91b 100644 --- a/docs/html/google/play/licensing/setting-up.jd +++ b/docs/html/google/play/licensing/setting-up.jd @@ -32,29 +32,25 @@ environment</a></li> </div> <p>Before you start adding license verification to your application, you need to set up your Google -Play publishing account, your development environment, and test accounts required to verify +Play publishing account, your development environment, and any test accounts required to verify your implementation.</p> <h2 id="account">Setting Up a Publisher Account</h2> <p>If you don't already have a publisher account for Google Play, you need to register for one -using your Google account and agree to the terms of service on the Google Play publisher site:</p> - -<p style="margin-left:2em;"><a -href="http://play.google.com/apps/publish">http://play.google.com/apps/publish</a> -</p> +using your Google account and agree to the Google Play terms of service.</p> <p>For more information, see <a href="{@docRoot}distribute/googleplay/publish/register.html">Get Started with Publishing</a>.</p> -<p>If you already have a publisher account on Google Play, use your existing -account to set up licensing.</p> +<p>If you already have a publisher account on Google Play, use your +Developer Console to set up licensing.</p> -<p>Using your publisher account on Google Play, you can:</p> +<p>Using the Google Play Developer Console, you can:</p> <ul> -<li>Obtain a public key for licensing</li> +<li>Obtain an app-specific public key for licensing</li> <li>Debug and test an application's licensing implementation, prior to publishing the application</li> <li>Publish the applications to which you have added licensing support</li> @@ -63,33 +59,35 @@ publishing the application</li> <h4>Administrative settings for licensing</h4> <p>You can manage several -administrative controls for Google Play licensing on the publisher site. The controls are available -in the Edit Profile page, in the "Licensing" panel, shown in figure 1. The controls +administrative controls for Google Play licensing in the Developer Console. The controls let you: </p> <ul> <li>Set up multiple "test accounts," identified by email address. The licensing server allows users signed in to test accounts on a device or emulator to send -license checks and receive static test responses.</li> -<li>Obtain the account's public key for licensing. When you are implementing -licensing in an application, you must copy the public key string into the -application.</li> +license checks and receive static test responses. You can set up accounts in the +Account Details page of the Developer Console.</li> <li>Configure static test responses that the server sends, when it receives a license check for an application uploaded to the publisher account, from a user -signed in to the publisher account or a test account.</li> +signed in to the publisher account or a test account. You can set test responses +in the Account Details page of the Developer Console.</li> +<li>Obtain the app's public key for licensing. When you are implementing +licensing in an application, you must copy the public key string into the +application. You can obtain the app's public key for licensing in the Services +& APIs page (under All Applications).</li> </ul> - -<img src="{@docRoot}images/licensing_public_key.png" alt=""/> -<p class="img-caption"><strong>Figure 1.</strong> The Licensing -panel of your account's Edit Profile page lets you manage administrative -settings for licensing.</p> +<div style="width:640px;"> +<img src="{@docRoot}images/licensing_public_key.png" class="frame"> +<p class="img-caption"><strong>Figure +2.</strong> An app's license key is available from the Services & APIs page in +the Developer Console.</p> +</div> <p>For more information about how to work with test accounts and static test responses, see <a href="#test-env">Setting Up a Testing Environment</a>, below. - <h2 id="dev-setup">Setting Up the Development Environment</h2> <p>Setting up your environment for licensing involves these tasks:</p> @@ -432,9 +430,9 @@ Setting up a Library Project</a>.</p> <h2 id="test-env">Setting Up the Testing Environment</h2> -<p>The Google Play publisher site provides configuration tools that let you +<p>The Google Play Developer Console provides configuration tools that let you and others test licensing on your application before it is published. As you are -implementing licensing, you can make use of the publisher site tools to test +implementing licensing, you can make use of the Developer Console tools to test your application's Policy and handling of different licensing responses and error conditions.</p> @@ -487,10 +485,12 @@ href="{@docRoot}google/play/licensing/licensing-reference.html#server-response-c Response Codes</a> in the <a href="{@docRoot}google/play/licensing/licensing-reference.html">Licensing Reference</a>.</p> -<img src="{@docRoot}images/licensing_test_response.png" alt=""/> -<p class="img-caption"><strong>Figure 4.</strong> The Licensing -panel of your account's Edit Profile page, showing the Test Accounts field and the -Test Response menu.</p> +<div style="width:640px;"> +<img src="{@docRoot}images/licensing_test_response.png" class="frame"> +<p class="img-caption"><strong>Figure 4.</strong> The License Testing +panel of your Account details page lets you set up test accounts and +manage test responses.</p> +</div> <p>Note that the test response that you configure applies account-wide — that is, it applies not to a single application, but to <em>all</em> @@ -516,7 +516,7 @@ test responses available and their meanings. </p> <p>In some cases, you might want to let multiple teams of developers test licensing on applications that will ultimately be published through your publisher account, but without giving them access to your publisher account's -sign-in credentials. To meet that need, the Google Play publisher site lets +sign-in credentials. To meet that need, the Google Play Developer Console lets you set up one or more optional <em>test accounts</em> — accounts that are authorized to query the licensing server and receive static test responses from your publisher account.</p> @@ -609,13 +609,13 @@ upload a new version if the local application increments the <p>The licensing server handles static test responses in the normal way, including signing the license response data, adding extras parameters, and so -on. To support developers who are implementing licensing using test accounts, +on. To support developers who are implementing licensing using test accounts rather than the publisher account, you will need to distribute -your public key to them. Developers without access to the publisher site do not -have access to your public key, and without the key they won't be able to -verify license responses. </p> +the app's public key for licensing to them. Developers without access to the +Developer Console do not have access to the app's public key, and without +the key they won't be able to verify license responses. </p> -<p>Note that if you decide to generate a new licensing key pair for your account +<p>Note that if you decide to generate a new licensing key pair for the app for some reason, you need to notify all users of test accounts. For testers, you can embed the new key in the application package and distribute it to users. For developers, you will need to distribute the new key to them @@ -661,7 +661,7 @@ href="#runtime-setup">Setting up the runtime environment</a>, above.</p> <p>Signing in using a publisher account offers the advantage of letting your applications receive static test responses even before the applications are -uploaded to the publisher site.</p> +uploaded to the Developer Console.</p> <p>If you are part of a larger organization or are working with external groups on applications that will be published through your site, you will more likely diff --git a/docs/html/images/billing_public_key.png b/docs/html/images/billing_public_key.png Binary files differdeleted file mode 100644 index a0620f8..0000000 --- a/docs/html/images/billing_public_key.png +++ /dev/null diff --git a/docs/html/images/gp-buyer-currency.png b/docs/html/images/gp-buyer-currency.png Binary files differindex 51b8108..96d7e65 100644 --- a/docs/html/images/gp-buyer-currency.png +++ b/docs/html/images/gp-buyer-currency.png diff --git a/docs/html/images/gp-dc-countries.png b/docs/html/images/gp-dc-countries.png Binary files differindex 00d0d5e..72ce796 100644 --- a/docs/html/images/gp-dc-countries.png +++ b/docs/html/images/gp-dc-countries.png diff --git a/docs/html/images/gp-dc-details.png b/docs/html/images/gp-dc-details.png Binary files differindex 567567e..5b7eba4 100644 --- a/docs/html/images/gp-dc-details.png +++ b/docs/html/images/gp-dc-details.png diff --git a/docs/html/images/gp-dc-home.png b/docs/html/images/gp-dc-home.png Binary files differindex 381d0db..5ed46c9 100644 --- a/docs/html/images/gp-dc-home.png +++ b/docs/html/images/gp-dc-home.png diff --git a/docs/html/images/gp-dc-profile.png b/docs/html/images/gp-dc-profile.png Binary files differindex e526369..e254e5d 100644 --- a/docs/html/images/gp-dc-profile.png +++ b/docs/html/images/gp-dc-profile.png diff --git a/docs/html/images/gp-dc-reviews.png b/docs/html/images/gp-dc-reviews.png Binary files differindex cab175a..4290136 100644 --- a/docs/html/images/gp-dc-reviews.png +++ b/docs/html/images/gp-dc-reviews.png diff --git a/docs/html/images/gp-dc-stats-mini.png b/docs/html/images/gp-dc-stats-mini.png Binary files differindex d29a270..211b5ea 100644 --- a/docs/html/images/gp-dc-stats-mini.png +++ b/docs/html/images/gp-dc-stats-mini.png diff --git a/docs/html/images/gp-dc-stats.png b/docs/html/images/gp-dc-stats.png Binary files differindex 06f88e5..7df6266 100644 --- a/docs/html/images/gp-dc-stats.png +++ b/docs/html/images/gp-dc-stats.png diff --git a/docs/html/images/gp-devconsole-home.png b/docs/html/images/gp-devconsole-home.png Binary files differindex 1d758fd..a86f591 100644 --- a/docs/html/images/gp-devconsole-home.png +++ b/docs/html/images/gp-devconsole-home.png diff --git a/docs/html/images/gp-supported-dev-requirements.png b/docs/html/images/gp-supported-dev-requirements.png Binary files differindex d84f34e..c38b8aa 100644 --- a/docs/html/images/gp-supported-dev-requirements.png +++ b/docs/html/images/gp-supported-dev-requirements.png diff --git a/docs/html/images/licensing_public_key.png b/docs/html/images/licensing_public_key.png Binary files differindex 1630209..a3cd785 100644 --- a/docs/html/images/licensing_public_key.png +++ b/docs/html/images/licensing_public_key.png diff --git a/docs/html/images/licensing_test_response.png b/docs/html/images/licensing_test_response.png Binary files differindex ead2152..219ae24 100644 --- a/docs/html/images/licensing_test_response.png +++ b/docs/html/images/licensing_test_response.png |
