Reminder: By Aug 31, 2025, all new apps and updates to existing apps must use Billing Library version 7 or newer. If you need more time to update your app, you can request an extension until Nov 1, 2025. Learn about
Play Billing Library version deprecation.
Google Play Billing Library version deprecation
Stay organized with collections
Save and categorize content based on your preferences.
As announced at Google I/O in 2019 and the
Meet Google Play Billing Library Version 3 blog post, all versions of Play
Billing Library will follow a two year deprecation cycle.
This topic answers common questions regarding Billing Library version
deprecation and migrating to newer versions.
Support timeline For different versions
| Version (including
minor versions)
|
Last date version can be
used to release new apps
or updates to existing
apps |
Extension request can be
made up to date
|
| 5 |
Aug-31-2024 |
Nov-1-2024 |
| 6 |
Aug-31-2025 |
Nov-1-2025 |
| 7 |
Aug-31-2026 |
Nov-1-2026 |
| 8 |
Aug-31-2027 |
Nov-1-2027 |
- How can I find which APK or App Bundle is triggering a deprecation warning?
- Review your project's imported dependencies (for example, those found
in your project's
build.gradle file). To be compliant, apps
must import a supported version as indicated in the table. Note that
Billing dependencies would be found only in APKs that require the
com.android.vending.BILLING permission.
- An APK or App Bundle that I no longer maintain is using a deprecated version of the Play Billing Library. Do I need to update?
- We strongly recommend updating all APKs to the latest version of the
Play Billing Library. However, if an APK is no longer maintained, then
no action is required for the APK at this time. This deprecation
prevents only new apps and updates from using older versions of the
Play Billing Library. Existing apps that use a deprecated version of
the library will continue to function as expected. Please ensure that all
actively maintained APKs are updated.
- How to fix APK or App Bundle updated to latest Play Billing Library but still triggering deprecation warning?
- Make sure your
AndroidManifest.xml contains an entry with name
com.google.android.play.billingclient.version. If the entry
isn't present, check your
manifest merge settings
to see if the manifest attribute is being dropped during manifest merging.
- How can I upgrade from an earlier version of Play Billing Library?
Update the dependency in your release to use a supported version as indicated
in the table. To see what changed between releases, read the
release notes.
In addition, we have an in-depth guide for migrating
to PBL 8.
Where can I find the extension form to continue distributing to all Google
Play users until 1 November?
If your app is still using an out of date Play Billing Library version, you'll
receive a warning and an inbox message in Play Console. The extension form is
available through the details page of the warning or issue on the
Policy status page in Play Console.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-07-08 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-08 UTC."],[],[],null,["# Google Play Billing Library version deprecation\n\nAs announced at Google I/O in 2019 and the\n[Meet Google Play Billing Library Version 3](https://android-developers.googleblog.com/2020/06/meet-google-play-billing-library.html \"Play Billing Library Version 3 Blog\") blog post, all versions of Play\nBilling Library will follow a two year deprecation cycle.\n\nThis topic answers common questions regarding Billing Library version\ndeprecation and migrating to newer versions.\n\nSupport timeline For different versions\n---------------------------------------\n\n| Version (including minor versions) | Last date version can be used to release new apps or updates to existing apps | Extension request can be made up to date |\n|------------------------------------|-------------------------------------------------------------------------------|------------------------------------------|\n| 5 | Aug-31-2024 | Nov-1-2024 |\n| 6 | Aug-31-2025 | Nov-1-2025 |\n| 7 | Aug-31-2026 | Nov-1-2026 |\n| 8 | Aug-31-2027 | Nov-1-2027 |\n\n**How can I find which APK or App Bundle is triggering a deprecation warning?**\n: Review your project's imported dependencies (for example, those found\n in your project's `build.gradle` file). To be compliant, apps\n must import a supported version as indicated in the table. Note that\n Billing dependencies would be found only in APKs that require the\n `com.android.vending.BILLING` permission.\n\n**An APK or App Bundle that I no longer maintain is using a deprecated version of the Play Billing Library. Do I need to update?**\n: We strongly recommend updating all APKs to the latest version of the\n Play Billing Library. However, if an APK is no longer maintained, then\n no action is required for the APK at this time. This deprecation\n prevents only new apps and updates from using older versions of the\n Play Billing Library. Existing apps that use a deprecated version of\n the library will continue to function as expected. Please ensure that all\n actively maintained APKs are updated.\n\n**How to fix APK or App Bundle updated to latest Play Billing Library but still triggering deprecation warning?**\n: Make sure your `AndroidManifest.xml` contains an entry with name\n `com.google.android.play.billingclient.version`. If the entry\n isn't present, check your\n [manifest merge settings](/studio/build/manage-manifests#merge-manifests)\n to see if the manifest attribute is being dropped during manifest merging.\n\n**How can I upgrade from an earlier version of Play Billing Library?**\n\n: Update the dependency in your release to use a supported version as indicated\n in the table. To see what changed between releases, read the\n [release notes](/google/play/billing/release-notes).\n\n In addition, we have an in-depth guide for migrating\n [to PBL 8](/google/play/billing/migrate-gpblv8).\n\n**Where can I find the extension form to continue distributing to all Google\nPlay users until 1 November?**\n\nIf your app is still using an out of date Play Billing Library version, you'll\nreceive a warning and an inbox message in Play Console. The extension form is\navailable through the details page of the warning or issue on the\n[Policy status](https://play.google.com/console/developers/app/policy-center \"Policy Center\") page in Play Console."]]
