Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PlayBilling version to V6 #476

Merged
merged 3 commits into from
Jul 24, 2024
Merged

Update PlayBilling version to V6 #476

merged 3 commits into from
Jul 24, 2024

Conversation

orbital17
Copy link
Collaborator

@orbital17 orbital17 commented Jul 22, 2024

WIP: API updates for Play Billing V6 migration

Copy link

google-cla bot commented Jul 22, 2024

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.

Copy link
Contributor

@PEConn PEConn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just one thought.

fail("Price change confirmation flow ended with result: " + result);
}
});
fail("Price change confirmation flow is not supported");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can fail earlier. At the moment, the PaymentActivity is launched, it connects to Play Billing (which is async) and queries the SKUs (which is async) then hits this, but we know in PaymentActivity#onCreate if the request is for a price change confirmation flow.

I think you could instead add if (mMethodData.isPricechangeConfirmation) { fail(...) } as soon as we create the MethodData.

@PEConn
Copy link
Contributor

PEConn commented Jul 24, 2024

To check, you've run the tests locally and they still pass, right?

@orbital17
Copy link
Collaborator Author

To check, you've run the tests locally and they still pass, right?

Yes, tests pass locally

@PEConn PEConn merged commit 653bfd2 into GoogleChrome:main Jul 24, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants