You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[in_app_purchase] Update to Google Play Billing Library 8.x #171523
Hi,
I’m using the in_app_purchase Flutter plugin in my app "Helty Home", currently published on the Google Play Store.
Today I received a critical message from the Google Play Console informing me that my app is using a deprecated version of the Google Play Billing Library, and that I need to update to version 7.0.0 or later before August 31, 2025 to continue publishing updates.
"Your app is using a version of Google Play Billing Library that will be deprecated soon. Starting August 31, 2025, all apps must use version 7.0.0 or later."
"We recommend upgrading to version 8 to benefit from the latest monetization features."
Can you please confirm if the plugin is planning to support Billing Library v7 or v8 soon?
If there's an existing issue or plan to migrate, I’d appreciate a link or estimated timeline so we can plan accordingly.
Thanks a lot for your work!
Proposal
Upgrade in android billing client to v8 (build.gradle) "implementation"
Reacted by Jake Noble, K9i - Kota Hayashi, Odatetsu, Alex S Hong, maRci002, Martin Sellergren, Stargaze, Onur Hazar, george-kim-8, Liwei.Liu and 2 more
Again, please use #171499 if there is additional information to provide about the warning about using a version <7. This issue is only tracking updating from 7.1 to 8.x.
Thanks for getting this in @jmagman and @gmackall !
What's the process of using the new version in combination with in_app_purchase? The current version of in_app_puchase is not compatible with the latest version of in_app_purchase_android. Will it work if we do a dependency override, or will we need to wait for the next major version update of in_app_puchase?
Re-opening since updating the in_app_purchase->in_app_purchase_android dependency hasn't happened yet, and needs an explicit step due to the major version change in the implementation package.
@jmagman Are there any behavioral breaks that affect the cross-platform interface (i.e., clients of just the app-facing package)? From the migration guide in the PR it sounds like probably not, but if there are we need to do a major version change in in_app_purchase as part of the bump, otherwise it's just a minor bump.
Reacted by Abel Putnoki, Ivelin Krastev and xv-ricky-p
@Hari-07 as mentioned before, this hasn't been included in in_app_purchase yet (as far as I'm aware?) so the issue still remains.
Why close the issue again?
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
[-]Upgrade billing client to v8 in android[/-][+][in_app_purchase] Update to Google Play Billing Library 8.x[/+]stuartmorgan-g commentedon Jul 2, 2025
in_app_purchasestarted using 7.1.x in January.There is not yet a timeline for adopting 8.x, as it was only released two days ago.
jjcr11 commentedon Jul 2, 2025
lillogoal commentedon Jul 2, 2025
@stuartmorgan-g yes no problem, I wanted to contribute to the community by informing about the warning from the Play Store
I'm using ^3.2.0 version
stuartmorgan-g commentedon Jul 2, 2025
The fact that people are (for reasons that are not yet clear) receiving a warning saying they are using a version less than 7 is tracked in #171499
lillogoal commentedon Jul 2, 2025
jakenoble commentedon Jul 8, 2025
ujwal-yadav-aot commentedon Jul 8, 2025
lillogoal commentedon Jul 8, 2025
jakenoble commentedon Jul 8, 2025
stuartmorgan-g commentedon Jul 8, 2025
Again, please use #171499 if there is additional information to provide about the warning about using a version <7. This issue is only tracking updating from 7.1 to 8.x.
17 remaining items
putnokiabel commentedon May 29, 2026
Thanks for getting this in @jmagman and @gmackall !
What's the process of using the new version in combination with
in_app_purchase? The current version ofin_app_puchaseis not compatible with the latest version ofin_app_purchase_android. Will it work if we do a dependency override, or will we need to wait for the next major version update ofin_app_puchase?stuartmorgan-g commentedon May 29, 2026
Re-opening since updating the
in_app_purchase->in_app_purchase_androiddependency hasn't happened yet, and needs an explicit step due to the major version change in the implementation package.@jmagman Are there any behavioral breaks that affect the cross-platform interface (i.e., clients of just the app-facing package)? From the migration guide in the PR it sounds like probably not, but if there are we need to do a major version change in
in_app_purchaseas part of the bump, otherwise it's just a minor bump.jmagman commentedon May 29, 2026
The breaking change in
in_app_purchase_androidwas the removal ofqueryPurchaseHistory, and that wasn't used in the interface. So minor bump.@gmackall thanks for pushing the
in_app_purchase_androidthrough to the end. Can you take care bumpingin_app_purchasehttps://github.com/flutter/packages/blob/0bceb6429cb5f46cafee519f51e924c1b53d3199/packages/in_app_purchase/in_app_purchase/pubspec.yaml#L24?
putnokiabel commentedon Jun 3, 2026
@Hari-07 as mentioned before, this hasn't been included in
in_app_purchaseyet (as far as I'm aware?) so the issue still remains.Why close the issue again?
Hari-07 commentedon Jun 3, 2026
I didn't. I wasn't even looking at this issue so that's weird
Reopening it
stuartmorgan-g commentedon Jun 3, 2026
GitHub has a very unfortunate behavior where syncing a PR that closed a (since-reopened) issue into a personal fork can re-close the issue.
[in_app_purchase] Bump `in_app_purchase_android` version from `0.4.x`…
[in_app_purchase_android] Update Play Billing library to 8.0.0 (flutt…
[in_app_purchase] Bump `in_app_purchase_android` version from `0.4.x`…
github-actions commentedon Jul 14, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.