Fix: Fix crash when querying in-app purchases#454
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
Fixed a crash that could happen when querying in-app purchases or subscriptions from Google Play.
Technical Context
BillingClientConnectionused manualsuspendCoroutinecallback bridging for billing API calls. Google's Billing Library can occasionally invoke async callbacks more than once (race inBillingClientImpl), andSafeContinuationthrowsIllegalStateException: Already resumedon the second invocationqueryPurchasesAsync,acknowledgePurchase,queryProductDetailsAsync) with billing-ktx's built-in suspend extension functions, which handle callback bridging internallybilling-ktx:8.0.0was already a dependency but wasn't being used for these calls