Releases notes

Play Billing Library 1.0 Release (2017-09-19, Announcement)

Important changes

• Embedded billing permission inside library’s manifest. It's not necessary to add the com.android.vending.BILLING permission inside Android manifest anymore.
• New builder added to BillingClient.Builder class.
• Introduced builder pattern for SkuDetailsParams class to be used on methods to query SKUs.
• Several API methods were updated for consistency (the same return argument names and order).

Behavior changes

BillingClient.Builder class

BillingClient.Builder is now initialized via the newBuilder pattern:

mBillingClient = BillingClient.newBuilder(context).setListener(this).build();

launchBillingFlow method is now called using a BillingFlowParams class

To initiate the billing flow for an in-app purchase or subscription, the launchBillingFlow() method receives a BillingFlowParams instance initialized with parameters specific to the request:

BillingFlowParams.newBuilder().setSku(skuId)
                              .setType(billingType)
                              .setOldSkus(oldSkus)
                              .build();

// Then, use the BillingFlowParams to start the purchase flow
int responseCode = mBillingClient.launchBillingFlow(builder.build());

New way to query available products

Arguments for queryPurchaseHistoryAsync() and querySkuDetailsAsync() methods were wrapped into a Builder pattern:

SkuDetailsParams.Builder params = SkuDetailsParams.newBuilder();
params.setSkusList(skuList)
      .setType(itemType);
mBillingClient.querySkuDetailsAsync(params.build(), new SkuDetailsResponseListener() {...})

The result is now returned via result code and a list of SkuDetails objects instead of previous wrapper class for your convenience and to be consistent across our API:

public void onSkuDetailsResponse(@BillingResponse int responseCode, List<SkuDetails> skuDetailsList)

Parameters order changed on onConsumeResponse() method

The order of arguments for onConsumeResponse from the ConsumeResponseListener interface has changed to be consistent across our API:

public void onConsumeResponse(@BillingResponse int responseCode, String outToken)

Unwrapped PurhaseResult object

PurchaseResult has been unwraped to be consistent across our API:

void onPurchaseHistoryResponse(@BillingResponse int responseCode, List<Purchase> purchasesList)

Bug fixes

• No response code in PURCHASES_UPDATED Bundle
• Fix ProxyBillingActivity and PurchasesUpdatedListener issues during device rotation

Developer Preview 1 Release (2017-06-12, Announcement)

Developer preview launched, aimed to simplify the development process when it comes to billing, allowing developers to focus their efforts on implementing logic specific to the Android app, such as application architecture and navigation structure.

The library includes several convenient classes and features for you to use when integrating your Android apps with the In-app Billing API. The library also provides an abstraction layer on top of the Android Interface Definition Language (AIDL) service, making it easier for developers to define the interface between the app and the In-app Billing API.