PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Registering the application in the Google Play Developer console
  • Creating an "In-App" product
  • Running the test of an "In-App" product
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
A specific configuration is required to manage the In-App purchases in an Android application.
This help page presents the different operations to perform.
The different steps are as follows:
Registering the application in the Google Play Developer console
To register the application:
  1. Connect to the Google Play developer console.
    Caution: A Google developer account is required as well as a Google Wallet account in order to sell products.
  2. Add the application and specify the requested information (title, description, ...).
  3. Display (if necessary) the characteristics of the application and select "Services & API".
  4. Write down the public license key of the application. This key must be copied into the wizard for generating the Android application if your application is using the inAppXXX functions of WLanguage.
Creating an "In-App" product
To create an "In-App" product:
  1. Generate the Android application in WINDEV Mobile. The generated application must be signed with your key file (don't use a generic signature).
  2. In the Google Play developer console, select the application that was added beforehand and select "APK file"
  3. Click "Import a new APK file" and select the APK file generated by WINDEV Mobile (this file is found in the Exe directory of the project).
  4. In "Products integrated to the application", click "Add a new product".
    Important: Select the "Supported product" type. The other types of products are not supported by the "In-App" functions of WINDEV Mobile.
    In "Products integrated to the application", click "Add a new product". Choose the type of product to add: Product managed or subscription
  5. Type the product identifier: any identifier can be used. This identifier will be used in the WLanguage code of the application in order to retrieve information about the product (inAppListProductInfo).
  6. Specify the other information about the product: title, description, price, ...Specify the other information about the product: title, description, price, recurrence of invoicing for the subscriptions, ...
  7. Save the created product and enable this product so that it can be sold.
Note: A few hours can pass between the time when the APK file of the application is imported and the time when the Google Play service takes the new version of the application into account.
Running the test of an "In-App" product
The test of "In-App" products can be run in your application without having to perform any financial transaction. To do so, the application must be published on Google Play Store in alpha version or in beta version.
In this case, you must add the gmail accounts of the users allowed to run the application test.
Caution:
  • This account must be saved on the device on which the application to test will be installed. If several accounts are saved on the device, the account used will be the one that downloaded the application. If the application was not downloaded, the first account of the list will be used.
  • The account used for the tests MUST NOT be the one used to connect to the Google Play developer console.
To run the application test:
  1. Install the application on your device (the emulator cannot be used).
    Important: The application installed must have:
    • a version identical to the one whose APK was imported into the developer console (same version numbers and same code version)
    • the same signature as the APK imported into the developer console.
      Import the new version of the application in the developer console if necessary.
  2. Run the application test.
Minimum required version
  • Version 19
Comments
Click [Add] to post a comment