Google IAP V3 plugin requires a fix to support apps that have more than 20 managed in-app products

Solar2D General Questions/Discussion
#1

This issue only affects apps that use the Google Play IAP V3 plugin.

Our app has more than 20 managed in-app products. If the user owns more than 20 managed products, the querySkuDetails() method in the IabHelper class will return with the failed response code (5) because it calls the IInAppBillingService.getSkuDetails() method which fails if the number of queried SKUs is greater than 20.

This thread explains the problem as it was first sent to Google: https://code.google.com/p/marketbilling/issues/detail?id=123

This link shows the relevant changes that need to be made to IabHelper.querySkuDetails() to break up the products list into groups of 20: https://gist.github.com/tanis2000/8824514

We compared the decompiled plugin.google.iap.v3.util.IabHelper to the copy of IabHelper.java from the Google Play IAP V3 sample app and have verified that the querySkuDetails() method are the same (i.e. both do not include the fix to break up the product list).

When we applied the changes (from the link above) to break up the product list in the sample app, the call to IabHelper.querySkuDetails() succeeded.

Please look into applying the fix to the Corona plugin as this is a major roadblock for apps that have many in-app products.

Thanks.

#2

Can you please file a bug report for this?

Thanks

Rob

#3

Hi Rob,

We’ve submitted a bug report (#38448) for this issue.

Thanks.

Edit: added case number for bug report.

#4

Thanks for posting the case ID!

Rob

#5

Rob,

Thank you for your quick reply to this topic.  Normally we would have just submitted the bug by itself, but due to the time sensitive nature of this issue, we have duplicated the information here.  As I’m certain the Corona team is aware, Google Play will be sunsetting IAP v2 on the 27th.  This means that realistically we need to have a new build out to our users by the 24th to provide at least a small window of opportunity for updating the app.  Is it likely that this fix will see tomorrow or Saturday’s daily build?

Thank you in advance for any information you have on this.

#6

Hi Rob,

We haven’t heard back regarding this issue for some time now. As Google IAP V3 is now the only supported store API, this issue adversely affects all our customers who have made numerous in-app purchases in our title. Affected customers are no longer able to make any purchases at all, managed or unmanaged.

Do you have any news about the status of this issue from your team?

Thanks

#7

Hi Nix Hydra,

I flagged this again yesterday with the engineers, but I don’t have a predicted timeframe of a fix. It is flagged as a fairly high priority issue though, and I can continue to prompt it being fixed sooner than later.

Brent

#8

Hi Rob and Brent,

We received an email informing us that the issue has been addressed. We’ll build with 2015.2563 and let you know if we have any further issues.

Thanks

#9

Can you please file a bug report for this?

Thanks

Rob

#10

Hi Rob,

We’ve submitted a bug report (#38448) for this issue.

Thanks.

Edit: added case number for bug report.

#11

Thanks for posting the case ID!

Rob

#12

Rob,

Thank you for your quick reply to this topic.  Normally we would have just submitted the bug by itself, but due to the time sensitive nature of this issue, we have duplicated the information here.  As I’m certain the Corona team is aware, Google Play will be sunsetting IAP v2 on the 27th.  This means that realistically we need to have a new build out to our users by the 24th to provide at least a small window of opportunity for updating the app.  Is it likely that this fix will see tomorrow or Saturday’s daily build?

Thank you in advance for any information you have on this.

#13

Hi Rob,

We haven’t heard back regarding this issue for some time now. As Google IAP V3 is now the only supported store API, this issue adversely affects all our customers who have made numerous in-app purchases in our title. Affected customers are no longer able to make any purchases at all, managed or unmanaged.

Do you have any news about the status of this issue from your team?

Thanks

#14

Hi Nix Hydra,

I flagged this again yesterday with the engineers, but I don’t have a predicted timeframe of a fix. It is flagged as a fairly high priority issue though, and I can continue to prompt it being fixed sooner than later.

Brent

#15

Hi Rob and Brent,

We received an email informing us that the issue has been addressed. We’ll build with 2015.2563 and let you know if we have any further issues.

Thanks