AI & TechnologyPlay Billing Library 9: Migration Guide and 2027 Deadline

Google's deprecation table gives Play Billing Library 8 a deadline of August 31, 2027 for new apps and updates, with an extension deadline of November 1, 2027, so version 9 is the one to move to. Google says existing apps keep working. The rule applies to new apps and updates. If you ship with Flutter, the practical question is when your plugin moves, because as of today the official plugin and RevenueCat still use version 8.

The dates below come from Google's deprecation page and release notes, and the plugin facts from the flutter/packages and RevenueCat repositories and pub.dev, as listed in the sources. I checked each one on October 18, 2026.

Disclosure: App369 is my studio. I build and fix apps, including in-app purchases and subscriptions in Flutter, and the last section mentions what I sell. Google and RevenueCat don't pay me for anything on this page.

The deadlines

Google gives every Billing Library version a two-year deprecation cycle. Its table:

Source: Google Play Billing Library version deprecation, last updated September 9, 2026.

Google's FAQ also says:

• Existing apps still work. Unmaintained APKs don't need updates. New apps and updates must use supported versions.
• The extension form is in Play Console. An app on an unsupported version gets a warning. Open its details on the Policy status page to find the form.
• Check the manifest if a warning stays. The merged AndroidManifest.xml must contain com.google.android.play.billingclient.version.

If your app is still on version 7, read the version 7 to 8 guide first.

What changed in version 9

Version 9.0.0 was released on May 19, 2026. Per Google's release notes:

Version 9.1.0 was released on June 18, 2026. It adds Billing Choice APIs, including BillingClient.getBillingChoiceInfoAsync(), BillingChoiceInfo and BillingClient.showBillingProgramInformationDialog(). Google's release notes list no later 9.x release as of October 18, 2026.

How Google says to migrate

Google's guide for moving to version 9 uses 9.1.0 in its examples. The steps:

1. Update the dependency to com.android.billingclient:billing:9.1.0. For Kotlin extensions, add billing-ktx.
2. Skip the queryProductDetailsAsync change if you are on 8. Google says the onProductDetailsResponse signature change applies only to upgrades from version 7.
3. Remove the old APIs, if you still use any. Google's list includes SkuDetails, querySkuDetailsAsync, BillingClient.SkuType (use ProductType), QueryPurchaseHistoryParams, the no-argument enablePendingPurchases() and queryPurchasesAsync(String, listener). My reading: most of these were already removed in version 8, so an app that moved to 8 cleanly has probably dealt with them. Check your code for any that remain.
4. Consider automatic service reconnection. Google recommends it.
5. Handle new sub-response codes on the BillingResult from launchBillingFlow(): PAYMENT_DECLINED_DUE_TO_INSUFFICIENT_FUNDS, USER_INELIGIBLE and NO_APPLICABLE_SUB_RESPONSE_CODE.
6. Account for the error-code change and the nullable link from the table above.

Flutter apps: where the plugins stand

I found no Flutter plugin on version 9 yet. A pull request to update in_app_purchase_android to 9.1.0 (flutter/packages #12781), opened September 8, 2026, was still open and unmerged on October 18, 2026. As of October 18, 2026:

Two details:

• in_app_purchase_android 0.5.4 needs a recent Flutter. Its pubspec requires Flutter 3.44 or later and Dart 3.12.
• My advice: a plugin on version 8 is fine until Google's version 8 deadline. The deadline for new apps and updates is August 31, 2027. That leaves time for the plugin authors to move.

My advice: don't force version 9 into a Flutter app by overriding the plugin's Gradle dependency until the plugin supports it. The plugin's Dart and Kotlin code is built against the version 8 API. Wait for the release, then upgrade the package.

What to do now

This section is my advice, not Google's.

1. Find the version you ship. In a native app, check com.android.billingclient:billing in build.gradle. In Flutter, check in_app_purchase_android or purchases_flutter in pubspec.lock.
2. Watch the plugin changelogs. Check the in_app_purchase_android and RevenueCat changelogs once a month. When one mentions Billing Library 9, plan the upgrade.
3. Keep your Flutter version current. Each plugin release raises its minimum Flutter, and a late jump can mean fixing other build errors first.
4. Upgrade early in the cycle, not at the deadline. Google's extension to November 1, 2027 is a safety net, not a plan.
5. Test purchases and restores before you ship. Use Play Console license testers to buy, cancel and restore each product type.

For every other dated Apple, Google Play and Firebase requirement in 2026 and 2027, see App Store and Google Play deadlines for 2026 and 2027. The related Android target level requirement is in the target API 36 guide.

Need a hand?

If your in-app purchases break during the Billing Library upgrade, or you're not sure what your plugins need, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or send me a short description.