Play Console warns your billing library is outdated? Upgrade
Short answer: Google Play gives every version of its Play Billing Library a two-year life. When your app's version falls out of support, Play Console shows a warning, and new apps and updates must use a supported version before Google's deadline. Your current app keeps working for existing users, but you won't be able to ship updates until you upgrade. Check which version your app uses, plan the move to the latest supported version, and test purchases and subscriptions thoroughly before release, because the upgrade often involves code changes, not just a version number.
What the warning means
Android's deprecation FAQ explains that all versions of the Play Billing Library follow a two-year deprecation cycle. Each version has a deadline for new apps and updates, and a later extension deadline you can request if you need more time.
Google's published timeline at the time of writing:
- Version 7: new app and update deadline 31 August 2026, extension until 1 November 2026.
- Version 8: 31 August 2027, extension until 1 November 2027.
- Version 9: 31 August 2028, extension until 1 November 2028.
The documentation's reminder is direct: by 31 August 2026, all new apps and updates to existing apps must use Billing Library version 8 or later. As of November 2026, version 7's extension window has also closed, so an app still on version 7 or earlier needs upgrading before its next release.
Who is affected
Only apps that use Google Play's billing system: subscriptions, memberships, credits, premium unlocks and other in-app purchases. The FAQ notes that these dependencies only appear in apps that request the billing permission.
If your app takes payments for physical goods or services through a regular payment provider and doesn't use Play billing, this warning doesn't apply.
The FAQ also says unmaintained APKs don't need updates; existing apps still work. The pressure comes the moment you want to ship anything new, including an urgent bug fix.
Step 1: find your current version
Check the billing dependency in your app's build.gradle file. Look for com.android.billingclient:billing or the Kotlin variant billing-ktx.
If you use a cross-platform framework or a subscription management SDK, the billing library may come in through that dependency instead. In that case, upgrade the plugin or SDK to a release that bundles a supported version, and check its release notes for which billing version it uses.
Step 2: decide whether you need an extension
If the deadline is close and the upgrade involves real code changes, request an extension. The FAQ says apps using an unsupported version get a warning in Play Console; open the warning's details on the Policy status page to find the extension form. An extension buys time, not a permanent exception, so plan the work straight away and don't let the extension deadline arrive with the upgrade half finished.
Step 3: upgrade to the latest version
Google's migration guide for version 9 covers upgrades from versions 7 and 8. It notes that version 9 removes previously deprecated APIs and adds more detailed error information through new sub-response codes. The main steps are:
- Update the dependency version in
build.gradle, and the KTX module if you use Kotlin extensions. - If you're coming from version 7, update your code for product details queries, because the response listener's signature changed.
- Replace any removed APIs your app still calls, following the release notes and migration guide.
If you're on an older version than 7, read the release notes for each version in between. Several older patterns were removed along the way, and it's easier to fix them knowingly than to chase compiler errors.
Step 4: test real purchase flows
Billing bugs cost money and trust, so test more than "it compiles". Write down the expected result for each case before you start, and test on more than one device and Android version:
- buying each product and subscription plan you sell,
- restoring purchases after reinstalling the app,
- upgrades, downgrades and cancellations of subscriptions,
- pending or failed payments,
- what happens when the app is offline or the user backs out of the purchase screen.
Use Play's testing tracks and test accounts so you're not charging real cards. If your server verifies purchases or listens for subscription notifications, test those together with the app.
Step 5: fix false warnings
Sometimes the warning remains after you've upgraded. The FAQ suggests checking that your app's manifest contains the com.google.android.play.billingclient.version entry, and if it's missing, whether manifest merging is removing it.
Keep it from happening again
Billing upgrades become painful when they're left for years. A few habits help:
- Note the billing library version and its deadline in your project documentation.
- Review it at least yearly, well ahead of each August deadline.
- Keep purchase handling isolated in one part of the code, so upgrades touch fewer files.
- Keep automated tests or a written test script for purchase flows.
An illustrative example
A gym in Halifax has a member app that sells monthly class passes through Google Play. The developer tries to release a timetable fix and finds Play Console flagging the app's billing library as unsupported. The app is two major versions behind. They request an extension, upgrade to the latest version over two weeks, update the product details code, and test new purchases, renewals and cancellations with test accounts on an internal track. The timetable fix ships with the billing upgrade.
FAQ
Will the warning stop existing subscribers from renewing?
The FAQ says existing apps still work. The restriction applies to new apps and updates.
Can I skip straight to the newest version?
Yes, and it gives the longest runway. Read the release notes for every version you skip.
Does this affect iPhone apps?
No. Apple's in-app purchase system has its own requirements.
How long does an upgrade take?
It depends on how far behind you are and how purchase code is structured. Budget time for testing.
If your Android app's billing library is out of date and you need it upgraded and tested, tell us how your app sells today.