Core 2.2.2 and IAP 2.2.7 - Purchases appear as non-consumables on Android

Just updated and the purchase I made for a consumable appears as non-consumable showed: "you already own this item".

After restarting the app it seemed to be running ok.

 

We never changed product types (they are all consumables).

This happened immediately after the update from a previous IAP version (2.2.1 & 1.22.0) on device.
After I restarted the app, purchases were working correctly again.

 

@John_Corbett
Unfortunately it seems that many of our players are now encountering this issue where the IAP is marked as non-consumable. The game has been live for 2 years and this error started happening right after the update to the latest version.

I'm happy to share the IAP manager code asap, let me know how to do it.

 

@John_Corbett @JeffDUnity3D
We are also seeing way more incorrect Product.transactionID... So instead of GPA.XXX.XXXX
we are seeing " jmlhhdppfdaaekhdfdehcgmb.AO-J1OxATc6UMKdXlb_c489hatdKYgcPv6Mbn-D8sDrNXlRW1KStBThW2v94nrsqw_V3-XXXXXXXXX-XXXXXX"

 

So to summarize we saw a few different errors when using the latest version, so we had to revert back to our previous setup.

Error #1: Google play recognizes a product as non-consumeable and the purchase fails but the customer is getting charged.

Error #2: The developer payload we were getting from the receipt is NAN.

Error #3: The transaction id is not GPA.XXXX.XXX but a different string (unsure if this is directly related but it happens more in new version).

 

@JeffDUnity3D
For the non-consumeable issue, here is what we know:
- Update the app from a previous version (core 2.2.1 & 1.22.0) to the latest.
- Try and make a purchase.
- A product will be recognized as a non-consumeable and will not be processed correctly.
- The request will not get to our server for receipt validation.
- Sometimes Google will automatically refund a player for this invalid purchase and sometime they won't.

For the NAN dev payload and incorrect transaction id issue, this is inconsistent but happens a lot more with the latest versions. After trying out multiple devices it will usually happen. Here is what we know:

- Happens to both new installs and to updated ones. It happened in the past (1/50 or 1/100 times) but it happens much more with the latest version.

- The request gets to our server but cannot be validated at the receipt appears invalid. After reopening the app and IAP inits again, we get the correct data for the process purchase and the server successfully validates the receipt.

Attached a reduced file of our IAP management process (client).

Finally, after reverting back to core 2.2.1 & 1.22.0, purchases are working correctly again.

 

Yes, I mean that the player will get this message.
We don't have any non-consumable items aside from a subscription which is irrelevant here.
The first time we saw this issue was after updating to the latest version.

We never saw a consumable showing this message before though so I figured it was acting as a non-consumeable, I didn't know that a consumeable will show it if you are in the process as we've never seen this happen before.

 

Just to be clear, did you mean ConfirmPendingPurchase ?

 

Got it, we will be investigating if we skipped a confirm pending purchase with the latest version.
@JeffDUnity3D any thoughts on the incorrect transaction id issue? Should I start a new thread regarding this?

 

Oh wow, that's quite a huge change. Moving to the other thread as this is becoming off-topic.