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.
- 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.gradlefile). To be compliant, apps must import version 4.0.0 or higher of the Play Billing Library. Note that Billing dependencies would be found only in APKs that require the
- 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.xmlcontains 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 v4 or higher of the Play Billing Library. To see what changed between releases, read the release notes.
In addition, we have an in-depth guide for migrating from PBL 4 to 5.