Play Billing Library 8 and Purchases SDK v9.0.0: Migration Checklist
Play Billing Library 8 changes how one-time products, subscriptions, product queries, and billing errors work. Purchases SDK v9.0.0 adds support across Android, Kotlin Multiplatform, Flutter, and React Native. Use this checklist to check your platform versions, decide how to handle historical purchases, and confirm whether your existing purchase code can stay in place.
What changed in Play Billing Library 8
Play Billing Library 8 renames in-app items to one-time products and lets those products carry multiple purchase options and offers. It also adds non-expiring subscriptions and new Kotlin extensions. For product lookup, queryProductDetailsAsync() now reports products that could not be fetched, including a product-level status code, and onProductDetailsResponse() has a changed signature that implementations must adjust to. BillingClient can reconnect automatically after a disconnect, so manual startConnection() calls after disconnections are no longer required. launchBillingFlow() can now return sub-response codes for specific failures, such as PAYMENT_DECLINED_DUE_TO_INSUFFICIENT_FUNDS. Deprecated APIs including querySkuDetailsAsync(), queryPurchaseHistory(), and the older enablePendingPurchases() form were removed in v8.
Migration decision checklist
Before upgrading, work through these checks in order: 1. Confirm your platform and language version meets the minimum for your SDK (see the platform checklist below). 2. If you are below the minimum, upgrade that dependency first; if you are at or above it, no extra platform change is needed for the v9 move. 3. Decide how historical purchases will be handled, because expired subscriptions and consumed one-time products can no longer be queried. 4. If you keep your own in-app purchase code, update the SDK and confirm Play Billing Library 8 or higher. 5. Review product-query and billing-flow error handling for the new status and sub-response codes.
Expired subscriptions and consumed products
Play Billing Library 8 removes the ability to query expired subscriptions and consumed one-time products. For a migration from a non-SDK implementation, that means the SDK cannot retrieve and send purchase data for those past transactions through that query path. The same historical data can still be imported through a backend historical import. Teams that already route all transactions through the SDK are not affected by this removal.
Keeping your own in-app purchase code
Keeping your own in-app purchase code alongside the SDK, previously called observer mode, is still supported in v9.0.0. Beyond updating the SDK version, no additional SDK changes are required for that setup. The requirement is to also use Play Billing Library version 8 or higher.
Platform version requirements
Android: SDK v9 uses Kotlin 2.0.21 and requires Kotlin 1.8.0 or higher. Below 1.8.0 is the main breaking change; at or above it, migration can proceed without additional changes. Where possible, use the latest released version, noted as 9.1.1 at the time of writing, for recent improvements and fixes. Kotlin Multiplatform: KMP SDK 2.0.0+15.0.0 uses Kotlin 2.1.10 and requires Kotlin 2.1.0 or higher; older versions must be updated first. React Native: SDK 9.0.0 uses Kotlin 2.0.21 and requires Kotlin 1.8.0 or higher; older versions must be upgraded. Flutter: SDK 9.0.0 requires Flutter 3.22.0 or higher and Dart 3.4.0 or higher; older versions must be upgraded.
Planning for future billing updates
Google typically releases a new Play Billing Library version each year, often around Google I/O, so keeping billing, platform, and SDK compatibility current is recurring work. The iOS SDK is not affected by these Google Play Billing updates.
| Platform | SDK version in scope | Minimum version required | Action if below minimum |
|---|---|---|---|
| Android | v9 (latest noted: 9.1.1) | Kotlin 1.8.0+ | Upgrade Kotlin; SDK uses Kotlin 2.0.21 |
| Kotlin Multiplatform | 2.0.0+15.0.0 | Kotlin 2.1.0+ | Upgrade Kotlin; SDK uses Kotlin 2.1.10 |
| React Native | 9.0.0 | Kotlin 1.8.0+ | Upgrade Kotlin; SDK uses Kotlin 2.0.21 |
| Flutter | 9.0.0 | Flutter 3.22.0+ and Dart 3.4.0+ | Upgrade Flutter and Dart |
Version requirements as captured in the supplied article; check the latest release for your platform before upgrading.
Frequently asked questions
Does the iOS SDK need to change for Play Billing Library 8?
No. The iOS SDK is not affected by these Google Play Billing changes.
Can I keep my own in-app purchase code with SDK v9.0.0?
Yes. Using the SDK alongside your own in-app purchase code remains supported in v9.0.0. Update the SDK version and ensure Play Billing Library 8 or higher is in use.
Can the SDK still retrieve expired subscriptions and consumed one-time products?
No, not through the SDK query path. Play Billing Library 8 removes that query capability. Past transaction data can still be brought in through a backend historical import.