Skip to content

[in_app_purchase] Update to Google Play Billing Library 8.x #171523

Closed

Description

@lillogoal

Use case

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"

Activity

  1. changed the title [-]Upgrade billing client to v8 in android[/-] [+][in_app_purchase] Update to Google Play Billing Library 8.x[/+] on Jul 2, 2025
  2. added
    platform-androidAndroid applications specifically
    packageflutter/packages repository. See also p: labels.
    team-androidOwned by Android platform team
    on Jul 2, 2025
  3. stuartmorgan-g commented on Jul 2, 2025

    @stuartmorgan-g
    Contributor

    Can you please confirm if the plugin is planning to support Billing Library v7 or v8 soon?

    in_app_purchase started using 7.1.x in January.

    There is not yet a timeline for adopting 8.x, as it was only released two days ago.

  4. jjcr11 commented on Jul 2, 2025

    @jjcr11
  5. lillogoal commented on Jul 2, 2025

    @lillogoal
    Author

    @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

  6. stuartmorgan-g commented on Jul 2, 2025

    @stuartmorgan-g
    Contributor

    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

  7. lillogoal commented on Jul 2, 2025

    @lillogoal
    Author
  8. jakenoble commented on Jul 8, 2025

    @jakenoble
  9. ujwal-yadav-aot commented on Jul 8, 2025

    @ujwal-yadav-aot
  10. lillogoal commented on Jul 8, 2025

    @lillogoal
    Author
  11. jakenoble commented on Jul 8, 2025

    @jakenoble
  12. stuartmorgan-g commented on Jul 8, 2025

    @stuartmorgan-g
    Contributor

    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.

  13. 17 remaining items

  14. putnokiabel commented on May 29, 2026

    @putnokiabel

    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?

  15. stuartmorgan-g commented on May 29, 2026

    @stuartmorgan-g
    Contributor

    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.

  16. jmagman commented on May 29, 2026

    @jmagman
    Member

    The breaking change in in_app_purchase_android was the removal of queryPurchaseHistory, and that wasn't used in the interface. So minor bump.

    @gmackall thanks for pushing the in_app_purchase_android through to the end. Can you take care bumping in_app_purchase https://github.com/flutter/packages/blob/0bceb6429cb5f46cafee519f51e924c1b53d3199/packages/in_app_purchase/in_app_purchase/pubspec.yaml#L24
    ?

  17. putnokiabel commented on Jun 3, 2026

    @putnokiabel

    @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?

  18. Hari-07 commented on Jun 3, 2026

    @Hari-07
    Member

    I didn't. I wasn't even looking at this issue so that's weird
    Reopening it

  19. reopened this on Jun 3, 2026
  20. stuartmorgan-g commented on Jun 3, 2026

    @stuartmorgan-g
    Contributor

    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.

  21. github-actions commented on Jul 14, 2026

    @github-actions

    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.

  22. locked as resolved and limited conversation to collaborators on Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listp: in_app_purchasePlugin for in-app purchasepackageflutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions