billing module still targets Play Billing Library 7.1.1 - timeline for Billing Library 8 (required by Play by Aug 31, 2026)?

[superdan77]

Read this First
If you have a Trusted Web Activity related question, the best place to ask it is on StackOverflow, on the
trusted-web-activity tag, which is also monitored by the team.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. It would be really cool if [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[superdan77]

Google Play now warns that all apps, including TWAs, must use Google Play Billing Library 8.0.0+ by Aug 31, 2026. The billing module in this repo is the dependency TWAs rely on for Play Billing via the Digital Goods API, but it still ships Billing Library 7.

What I verified

• Latest billing release is billing-1.1.0 (June 25, 2025), whose notes say "BillingClient library updated to 7.1.1".
• The main branch version catalog (gradle/libs.versions.toml) still declares billing = "7.1.1".

The problem

TWAs do not call the Billing Library directly. They go through com.google.androidbrowserhelper:billing. So even though com.android.billingclient:billing 8.x/9.x exists, TWA apps cannot satisfy the Play requirement until this bridge is updated to Billing 8.

Questions

1. Is there a planned release of the billing module that moves to Billing Library 8? Any rough timeline relative to the Aug 31, 2026 deadline?
2. Is manually overriding com.android.billingclient:billing to 8.x on top of the current androidbrowserhelper:billing:1.1.0 a supported workaround, or will it break because v8 removed APIs the bridge uses (querySkuDetailsAsync, queryPurchaseHistoryAsync)?
3. If no update lands in time, is requesting the Play Console extension to Nov 1, 2026 the expected path for TWA developers?

Thanks - this affects every TWA that uses Play Billing, so an official note on the plan would help a lot of us.

[carlosjeurissen]

For now you can request extension until November 1st. See the link from the email. However this only delays the issue. Any update on support for 8.0 would be greatly appreciated.

[t-heu]

Same problem here; I hope this version (8/9) fixes the issue with opening the billing screen, which doesn't work on Samsung devices.

[8designers]

Same problem here.

[carlosjeurissen]

Can the maintainers of the library let us know if they expect an update between now and the 1st of November, or should consumers of the Play Billing Library consider alternatives?

Seems it is considered a policy violation. Pretty alarming:

[carlosjeurissen]

Seems this is currently being worked on:
162380a

[JonathanIntrinsic]

Adding to what @carlosjeurissen spotted: the migration now looks complete on main, not just in progress.

As of today, gradle/libs.versions.toml reads billing = "8.3.0" and playbilling/build.gradle reads VERSION = "1.2.0" with versionCode 3. The six commits:

• 399d79d configure PendingPurchasesParams for one-time products (FR-04)
• ccbbb3a refactor queryPurchases to use QueryPurchasesParams (FR-06)
• 5f03be2 refactor BillingWrapper and implement product details mapping (FR-02, FR-05)
• d2ea99f make listPurchaseHistory return OK/empty list immediately and remove queryPurchaseHistory (FR-03)
• 162380a upgrade play billing library to v8.3.0 and fix listener compatibility (FR-01)
• a3638f2 bump play billing module version and versionCode (FR-07), dated 2026-07-28

The FR-07 version bump landing yesterday reads like the work is finished and ready to ship.

What is missing is a release. The newest tag is still billing-1.1.0 and Maven Central still serves 1.1.0, so bubblewrap's hardcoded com.google.androidbrowserhelper:billing:1.1.0 still resolves to Play Billing 7.1.1, and any TWA built through bubblewrap or PWABuilder declares com.google.android.play.billingclient.version = 7.1.1. That is the value Play scans.

So the concrete ask: could billing-1.2.0 be tagged and published to Maven Central? That single step unblocks every TWA that sells through the Digital Goods API, with about four weeks left before the deadline, and without anyone having to fork or build the module themselves.

I'm happy to test a release candidate against a live app if that is useful. Mine sells one-time non-consumable products only, so it exercises the INAPP / getOneTimePurchaseOfferDetails path plus queryPurchases and acknowledgment, and it does not touch listPurchaseHistory or the subscription offer paths.

[carlosjeurissen]

Seems to be released as 1.2.0 now:
https://github.com/GoogleChrome/android-browser-helper/releases/tag/billing-1.2.0