[in_app_purchase_android] Add obfuscated profile ID purchase param#12080
[in_app_purchase_android] Add obfuscated profile ID purchase param#12080lianshumin wants to merge 1 commit into
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 passing an obfuscated profile ID (obfuscatedProfileId) in GooglePlayPurchaseParam for the Android in-app purchase implementation, propagating it to the billing flow parameters, and adding a corresponding unit test. The review feedback suggests documenting that obfuscatedProfileId requires applicationUserName to be specified, and updating the unit test to include both parameters for a more realistic scenario.
fb6cfd2 to
ed03359
Compare
Adds an optional
obfuscatedProfileIdparameter toGooglePlayPurchaseParamand passes it through to Google Play Billing's
BillingFlowParams.Builder.setObfuscatedProfileId().This keeps the API Android-specific, since
setObfuscatedProfileId()is aGoogle Play Billing API and has no StoreKit equivalent. Existing behavior is
unchanged because the new parameter is optional.
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