Cant do a second purchase, after first success.

[Shabinder]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Describe the bug
After we have successfully purchased one product, and then try to complete another purchase of same or different product.
in same session, leads to happening nothing and any further purchases wont work since, we get The operation is already in progress

Doesn't get fixed until we restart the app.

1. Environment
   1. Platform: Android
   2. SDK version: 6.5.2
   3. OS version: 13
   4. How widespread is the issue: all I could test on.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[Shabinder]

purchases-android/common/src/main/java/com/revenuecat/purchases/google/BillingWrapper.kt

Line 253 in fb12997

log(LogIntent.PURCHASE, PurchaseStrings.PURCHASING_PRODUCT.format(googlePurchasingData.productId))

I do get logs on second purchase till this point.

Could the next line synchronized block could be the cause ?

Since my purchase's callbacks are not invoked for the second purchase.

[tonidero]

Hi @Shabinder, unfortunately I wasn't able to repro. I was able to purchase multiple products (or the same one after the first subscription expires if it's a subscription). I'm not sure what's happening since the This operation is already in progress error log means that the process should be cut before getting to the Purchasing product: ... log.

Could you send us debug logs of this situation happening so we can better debug the issue?

[Shabinder]

Simple logcat or any specific command / process to get debug logs ?

[tonidero]

You can enable debug logs by doing Purchases.logLevel = LogLevel.DEBUG BEFORE configuring the SDK. Docs here: https://www.revenuecat.com/docs/debugging

Once you do that, you can filter logcat logs that include [Purchases] and send them to us. Feel free to create a support ticket and it that way if you prefer, while linking to this issue.