Bug: Android QueryProduct fails with OpenIapError$QueryProduct

[quangtuan28200]

Description

On Android, querying products sometimes fails with OpenIapError$QueryProduct: Failed to query product.

The error appears from ProductManager$getOrQuery$3$1.onProductDetailsResponse, but the stack trace does not expose the original Google Billing response code/message, so it is difficult to debug whether this is caused by product configuration, Play Store state, billing availability, or library behavior.

Stack traces

dev.hyo.openiap.OpenIapError$QueryProduct: Failed to query product
at dev.hyo.openiap.helpers.ProductManager$getOrQuery$3$1.onProductDetailsResponse(ProductManager.kt:103)
at com.android.billingclient.api.BillingClientImpl.zzt(com.android.billingclient:billing@@8.3.0:13)
at com.android.billingclient.api.zzbf.call(Unknown Source:6)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)

dev.hyo.openiap.OpenIapError$QueryProduct: Failed to query product
at dev.hyo.openiap.helpers.ProductManager$getOrQuery$3$1.onProductDetailsResponse(ProductManager.kt:95)
at com.android.billingclient.api.BillingClientImpl.zzt(com.android.billingclient:billing@@8.3.0:13)
at com.android.billingclient.api.zzbf.call(Unknown Source:6)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)

Expected behavior

queryProduct / getProducts should either:

1. Return the available products/subscriptions successfully, or
2. Return a more detailed error including:
   • Billing response code
   • Billing debug message
   • Product IDs being queried
   • Product type: inapp or subs
   • Whether Google Billing returned an empty product list

Actual behavior

The app only receives:

OpenIapError$QueryProduct: Failed to query product

without enough details to identify the root cause.

Environment

• Platform: Android
• Library: openiap / react-native-iap
• Google Billing Client: billing@@8.3.0
• Product types used:
  • Subscriptions
  • Non-consumable lifetime product

Questions

1. Is this error usually caused by Google Play product configuration, or can it also happen due to Billing Client response handling?
2. Can the library expose the original BillingResult.responseCode and BillingResult.debugMessage in this error?
3. Is there any known issue around ProductManager.kt line 95 / 103 when Google Billing returns an empty product list?
4. What is the recommended way to debug which specific SKU/product ID failed?

Additional context

This issue happens while querying products before purchase. It may affect users who cannot see subscription or lifetime product details.

[gitdogbot]

@quangtuan28200 I read the relevant source files and can confirm the exact root cause.

Root Cause

There are two separate code paths that throw OpenIapError$QueryProduct, and they behave differently:

Path 1 — fetchProducts via ProductManager.kt ✅ Already fixed

In packages/google/openiap/src/play/java/dev/hyo/openiap/helpers/ProductManager.kt lines 103–109, the error is already constructed with full billing details:

val error = OpenIapError.QueryProduct(
    errorCode = billingResult.responseCode,
    debugMessage = billingResult.debugMessage,
    productIds = productList
)

Path 2 — queryProductDetails via BillingClientWrapper.kt ❌ The actual bug

In packages/google/openiap/src/play/java/dev/hyo/openiap/helpers/BillingClientWrapper.kt, the queryProductDetails function constructs the error differently. When the billing result is not OK, it throws:

throw OpenIapError.QueryProduct(
    errorCode = billingResult.responseCode,
    debugMessage = billingResult.debugMessage,
    productIds = emptyList()  // <-- productIds is lost here
)

The productIds field is populated with emptyList() instead of the actual list of product IDs that were queried. This means when the error propagates up to the caller, the productIds field in the error is always empty, making it impossible to know which products failed to load.

---

Fix

In BillingClientWrapper.kt, the queryProductDetails function receives the product ID list as a parameter. The fix is to pass that list through to the error constructor instead of emptyList().

Before

fun queryProductDetails(
    productIds: List<String>,
    productType: String
): List<ProductDetails> {
    // ...
    if (billingResult.responseCode != BillingClient.BillingResponseCode.OK) {
        throw OpenIapError.QueryProduct(
            errorCode = billingResult.responseCode,
            debugMessage = billingResult.debugMessage,
            productIds = emptyList()
        )
    }
    // ...
}

After

fun queryProductDetails(
    productIds: List<String>,
    productType: String
): List<ProductDetails> {
    // ...
    if (billingResult.responseCode != BillingClient.BillingResponseCode.OK) {
        throw OpenIapError.QueryProduct(
            errorCode = billingResult.responseCode,
            debugMessage = billingResult.debugMessage,
            productIds = productIds  // <-- pass the actual list
        )
    }
    // ...
}

---

Why This Matters

The productIds field in OpenIapError.QueryProduct exists specifically so callers can identify which products were involved in a failed query — for logging, retry logic, or surfacing a meaningful error message to the user. Passing emptyList() silently discards that context, making debugging significantly harder and preventing any retry logic from knowing what to re-query.

---

Summary

Location	Status	productIds in error
ProductManager.kt fetchProducts	✅ Correct	Populated with actual IDs
BillingClientWrapper.kt queryProductDetails	❌ Bug	Always emptyList()

The one-line fix is to replace emptyList() with productIds in the BillingClientWrapper.kt error constructor.

---

🤖 Generated by gitdog.dev · Have more questions? Tag @gitdog and let me know!

[hyochan]

@quangtuan28200 react-native-iap has now been published as 15.2.1.

• GitHub Release: https://github.com/hyodotdev/openiap/releases/tag/react-native-iap-15.2.1
• npm: https://www.npmjs.com/package/react-native-iap/v/15.2.1

The failed release runs in between did not publish to npm. The current latest version is 15.2.1.