Google Play Billing Library 8.0.0 Requirement: What Android Developers Need to Do Before August 31, 2026
If your Android app uses Google Play Billing for subscriptions or in-app purchases, there is an important update you should not ignore.
Google Play has been moving developers through a regular Play Billing Library deprecation cycle. For developers still using an older Billing Library version, the deadline for new apps and app updates is approaching.
From August 31, 2026, apps using Google Play Billing Library 7 or older will no longer meet the supported version requirement for new apps and updates. Developers should upgrade to Google Play Billing Library 8.0.0 or a newer supported version before submitting their next update.
If your project still uses an older Google Play Billing Library version, do not wait until the final day. Update the dependency, resolve any API changes, test your purchase flow and upload a new release well before the deadline.
What Is the Google Play Billing Library?
Google Play Billing Library is the Android library used by apps to communicate with Google Play's billing system. It allows developers to sell digital products, one-time purchases and subscriptions directly through Google Play.
For example, an Android application may use Google Play Billing for:
- Premium subscriptions
- One-time premium upgrades
- Removing advertisements
- Digital content purchases
- Additional features or functionality
- Recurring subscription plans
Google Play handles the payment process while the application uses the Billing Library to query products, launch the purchase flow and receive purchase information.
What Is Changing on August 31, 2026?
Google Play follows a deprecation cycle for its Play Billing Library versions. According to Google's current support timeline, Billing Library 7 has a new-app and update deadline of August 31, 2026.
This means developers maintaining Android applications should make sure their release uses a supported Billing Library version before the deadline.
The important point is that this is primarily a requirement for new apps and app updates. An older version already installed on a user's device does not simply stop functioning on the deadline.
Which Billing Library Versions Are Affected?
If your application is still using Billing Library 6, 7 or an even older version, you should review the project immediately.
The safest approach is not to wait until the minimum deadline version becomes unavoidable. Developers should consider upgrading to a currently supported version and test the complete billing implementation.
| Billing Version | New App / Update Deadline | Developer Action |
|---|---|---|
| Billing Library 6 | August 31, 2025 | Upgrade |
| Billing Library 7 | August 31, 2026 | Upgrade now |
| Billing Library 8 | August 31, 2027 | Supported |
| Billing Library 9 | August 31, 2028 | Current supported generation |
Google currently lists Billing Library 9.1.0 as available. Therefore, although developers may see messaging referring to version 8.0.0 as the minimum, it is worth evaluating whether upgrading directly to a newer supported release makes more sense for your project.
How to Check Which Google Play Billing Library Version Your App Uses
The first step is to find the Billing Library dependency in your Android project. Open the module-level build.gradle or build.gradle.kts file and search for:
com.android.billingclient:billingYou may find something similar to:
dependencies {
implementation "com.android.billingclient:billing:7.0.0"
}If the project contains Billing Library 7.0.0 or another unsupported version, it is time to plan the upgrade.
How to Upgrade to Google Play Billing Library 8.0.0
If you are migrating from Billing Library 6 or 7, Google provides an official migration path. The basic dependency change looks like this:
dependencies {
def billingVersion = "8.0.0"
implementation "com.android.billingclient:billing:$billingVersion"
}If your project uses Kotlin DSL, the syntax will normally look like:
dependencies {
implementation("com.android.billingclient:billing:8.0.0")
}However, changing the dependency alone may not be enough. Depending on the Billing Library version you are migrating from, your existing billing code may contain APIs that have changed or have been removed.
Important API Changes When Migrating to Billing Library 8
Billing Library 8 removes some APIs that had previously been deprecated. This is particularly important for applications with older subscription implementations.
For example, Google lists several subscription-related APIs that were removed when migrating from older versions.
| Older API | Replacement |
|---|---|
| setOldSkuPurchaseToken | setOldPurchaseToken |
| setReplaceProrationMode | setSubscriptionReplacementMode |
| setReplaceSkusProrationMode | setSubscriptionReplacementMode |
This is why developers should test their complete purchase and subscription implementation instead of simply changing the dependency version and assuming everything is finished.
What Changed in Google Play Billing Library 8?
Billing Library 8 introduced several improvements to the Play Billing system. One important change is the terminology around in-app items. Google now refers to these as one-time products.
Billing Library 8 also introduced support for multiple purchase options and offers for one-time products. This gives developers more flexibility when designing how digital products are sold.
Another important improvement affects queryProductDetailsAsync(). Billing Library 8 can return information about products that could not be fetched, along with a product-level status explaining the situation.
Developers should therefore review their product-query implementation when upgrading from an older Billing Library version.
What About Flutter Apps?
Flutter developers should pay particular attention to this requirement. If your Flutter application sells subscriptions or in-app purchases, the Android build can contain the Google Play Billing dependency indirectly through the Flutter billing or in-app-purchase package you are using.
This means you should not only check your own Android build.gradle file. You should also check which version of the relevant Flutter package and its Android dependencies are being resolved.
For Flutter projects, run your dependency commands and inspect the Android dependency tree when necessary. If an older plugin is pulling an unsupported Billing Library into your application, updating the plugin may be necessary.
After upgrading, create a release build and verify the resulting Android dependencies rather than assuming that the Flutter package update automatically solved everything.
Does This Affect Apps Without In-App Purchases?
Not every Android application needs the Play Billing Library.
If your application does not sell digital products, subscriptions or other Google Play-billed content, this particular Billing Library requirement may not apply to your app.
However, some applications may include the billing dependency through a third-party SDK or plugin. Developers should therefore inspect their final application dependencies if Google Play Console reports a Billing Library warning.
Will Existing Users Stop Being Able to Purchase?
The August 31, 2026 deadline is focused on the versions allowed for new apps and app updates. It does not mean that every existing APK using an older Billing Library will suddenly stop working at midnight on the deadline.
Google specifically distinguishes maintained apps that need updates from unmaintained existing APKs. Existing versions can continue to work, but developers who want to publish updates need to use a supported Billing Library version.
In practical terms, developers should treat the deadline as an update requirement, not as a reason to wait and see what happens.
What Should Android Developers Do Now?
- Open your Android project.
- Search for com.android.billingclient:billing.
- Identify the Billing Library version currently being used.
- Check whether a Flutter or Android plugin is bringing the dependency indirectly.
- Upgrade to Billing Library 8.0.0 or a newer supported release.
- Review deprecated and removed Billing APIs.
- Test one-time purchases.
- Test subscription purchases.
- Test subscription upgrades and downgrades if your app supports them.
- Test purchase restoration and entitlement handling.
- Test failed, cancelled and pending purchase scenarios.
- Build a release APK or AAB.
- Upload the release to a testing track in Google Play Console.
- Verify that the Billing Library warning has been resolved.
Do Not Forget Purchase Verification
Updating the Billing Library is only one part of a reliable in-app purchase implementation.
Google recommends using a secure backend for important billing operations, including purchase verification and subscription management. Your application should not blindly unlock premium content simply because the client reports that a purchase was successful.
A typical purchase flow involves displaying the product, launching the billing flow, verifying the purchase, granting the entitlement and acknowledging or consuming the purchase when appropriate.
This becomes especially important for applications where users pay for valuable premium features or subscriptions.
Should You Upgrade Only to 8.0.0?
Billing Library 8.0.0 satisfies the minimum version mentioned in the current Google Play warning, but developers should also look at newer supported releases.
Google has already released newer Billing Library versions. The official release notes currently list Billing Library 9.1.0.
Therefore, if your application can migrate cleanly to a newer supported version, it may be worth considering that option rather than performing multiple upgrades in a short period of time.
Don't select a Billing Library version only because it is the minimum accepted version. Check the current supported release, your Android Gradle setup, third-party plugins and the amount of migration work required before choosing your target version.
Common Problems After Updating Billing Library
Developers may encounter compilation or runtime problems after upgrading. Common areas to check include:
- Removed Billing APIs
- Changed method signatures
- Subscription replacement logic
- ProductDetails implementation
- Purchase acknowledgement
- Purchase restoration
- Pending purchases
- Third-party billing plugins
- Gradle dependency conflicts
- Release build dependency resolution
If your application has been using an older Billing Library for several years, expect the migration to require more than a single dependency change.
Frequently Asked Questions
What is the Google Play Billing Library 8.0.0 deadline?
The important 2026 deadline is August 31, 2026 for apps using Billing Library 7 or older that need to publish new apps or updates. Developers should move to Billing Library 8.0.0 or a newer supported version.
Is Google Play Billing Library 7 deprecated?
Yes. Google lists August 31, 2026 as the new-app and update deadline for Billing Library 7.
Can I use Google Play Billing Library 8.0.0?
Yes. Billing Library 8.0.0 is a supported generation, and Google provides a migration guide specifically for developers moving from Billing Library 6 or 7.
Is Billing Library 9 available?
Yes. Google has released Billing Library 9, and the current release notes list version 9.1.0. Developers should evaluate the latest supported version that works with their project.
Do Flutter apps need to update Google Play Billing?
If the Flutter application uses Google Play Billing through a plugin or package, the Android application can still be affected by the Play Billing requirement. Check the package and the final Android dependency tree.
Will Google Play reject my update if I use an old Billing Library?
Once the applicable deadline is reached, new apps and updates using an unsupported Billing Library version can no longer meet Google's requirements. Developers should update before submitting their next production release.
Final Thoughts
The Google Play Billing Library 8.0.0 requirement is another reminder that Android developers need to keep third-party libraries and platform dependencies up to date.
If your app uses subscriptions or in-app purchases and you are currently running Billing Library 7 or an older version, this should be treated as a priority. Do not wait until the final day to make the change.
Update the dependency, review the API changes, test every important purchase scenario and upload the release to a testing track before publishing it to production.
And if you are already planning the migration, consider whether moving directly to a newer supported Billing Library version makes more sense for your project than stopping at 8.0.0.
