[in_app_purchase_android] Update Play Billing library to 8.0.0 #10816
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates Play Billing Library to the latest version 8.0.0. Exposes new APIs as per release notes:
subResponseCodetoBillingResultWrapperandPlatformBillingResult.unfetchedProductListtoProductDetailsResponseWrapperandPlatformProductDetailsResponseto expose products that could not be retrieved.UnfetchedProductWrapper.oneTimePurchaseOfferDetailsListtoProductDetailsWrapperto support multiple one-time purchase offers.queryPurchaseHistorymethod onBillingClientWrapperas it has been removed from the native library (breaking change). Users should userestorePurchases(which usesqueryPurchasesAsyncinstead.This PR introduces breaking changes in
in_app_purchase_android, but does not introduce any breaking changes on the platform interface level.Fixes flutter/flutter#171523
Pre-Review Checklist
[shared_preferences]pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3