[in_app_purchase_android] Add obfuscated profile ID support#12079
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Code Review
This pull request adds support for obfuscatedProfileId in the Android implementation of the in_app_purchase plugin. Specifically, it introduces the obfuscatedProfileId parameter to GooglePlayPurchaseParam, passes it through buyNonConsumable in InAppPurchaseAndroidPlatform, and updates the corresponding unit tests to verify its serialization and transmission. There are no review comments, and I have no feedback to provide.
8cc9383 to
6b4e32b
Compare
Adds an Android-specific `obfuscatedProfileId` parameter to `GooglePlayPurchaseParam`, and passes it through to the Play Billing flow. Adds test coverage for passing account and profile identifiers through the platform purchase API.
Keeps the new release entry consistent with nearby in_app_purchase_android changelog formatting.
94bee43 to
13bd176
Compare
As mentioned in #130128, Google Play Billing supports passing an obfuscated profile ID in addition to an obfuscated account ID.
This adds an Android-specific
obfuscatedProfileIdparameter toGooglePlayPurchaseParam, and passes it through to the Play Billing flow.Fixes flutter/flutter#130128.
Pre-Review Checklist
[shared_preferences]///).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