"<productid> does not exist" from real device; method deprectation?

[BioTurboNick]

Received crash in the wild on an Android 6.0.1 device in Bolivia. ArgumentException <purchaseid> does not exist.

However, this purchase id is several years old and has been purchased successfully many times. I checked that the Play store shows it as active and available.

Only thing I can think of is that skuDetails can be null (the test used to throw this error) in other circumstances than the purchase id failing.

skuDetails originally comes from QuerySkuDetailsAsync (which is apparently deprecated in favor of QueryProductDetailsAsync now?)

I don't know if it's related to the deprecation, or if there's some (undocumented?) response code not being caught.

Bug Information

Version Number of Plugin: 6.7.0
Device Tested On: Android
Version of VS: 17.4.1
MAUI

[greg84]

I'm getting this too after migrating an app to MAUI and InAppBilling version 6.7.0.

The product is currently live, and in the Xamarin app it's being purchased now by users in production.

When I run the latest version of this plugin on an Android device with my MAUI version, I get the "{product id} does not exist" error.

Everything seems to be working fine on iOS.

@jamesmontemagno any ideas what could be causing this?

[greg84]

I cloned it so I could debug it. Even when I changed it to use QueryProductDetailsAsync it still came back with an empty list of products.

The response code comes back as "OK" for both QuerySkuDetailsAsync and QueryProductDetailsAsync.

I tried updating to billing API 5 too and it was still an empty product list.

[BioTurboNick]

If you're getting it every time, it might not be the same issue. Mine I haven't been able to reproduce.

[BioTurboNick]

FWIW - Some searching suggests QuerySkuDetailsAsync can be null if the billing client isn't connected, which could explain my issue? Say if it connects but the connection is interrupted before it can query? If so, then the null case just needs to be handled differently.

But for you Greg, if the response code is OK and the list is empty, that suggests a Google Play API/backend issue I think?

Unless something is wrong with the SkuDetailsParams passed in?

[greg84]

Thanks @BioTurboNick - you're right! I didn't have a bundle identifier set for Android so it was using the C# namespace, which obviously doesn't match the current app 🤦