[URGENT - LIVE VERSION] User has been charged but purchase isn't showing up about purchases-unity HOT 6 CLOSED

hi @melih-veloxia!! 👋

When a purchase is finished outside of the regular flow (i.e.: if there's a problem with the card, or if the user has to ask for parent's permission for a purchase, etc), the SDK will still provide a callback to the app.

This is done through the PurchaserInfoListener. Here are our docs explaining how to use it.

Basically in Unity you just make sure that you override the method PurchaserInfoReceived in the class that inherits from Purchases.UpdatedPurchaserInfoListener, then react to changes when the method gets called.

Hope this helps!

from purchases-unity.

@aboedo We managed to use this method but this method returns purchaserInfo what is your suggestion to determine which in app purchase is completed outside the game? Additionally, this listener is triggered when there is a purchase "inside" the game. That's why we decided to save a boolean variable if userCancelled is false and there is a STORE_ERROR . We check that boolean inside Purchases.UpdatedPurchaserInfoListener but this neither a bulletproof nor a solid method.

from purchases-unity.

purchaserInfo has information about entitlements, which in turn has information about the products the user has purchased.

We don't however have a specific way to know exactly which purchase just went through, sadly (this is in our backlog).

So the method you described (setting up the listener, then when the app is ready to do something with the purchased content, checking the value of purchaserInfo) should work.

Are there particular use cases that you're concerned about that wouldn't be covered by this?

from purchases-unity.

@aboedo entitlements returns only subscriptions, not the in-app-purchases. To check the in-app-purchases, I may use nonSubscriptionTransactions. To handle these kind of situations perfectly, I need to parse both entitlements and nonSubscriptionTransactions into our local database and check the latest ones, match it with the latest failed one, then mark them as rewardGiven to avoid reward duplication. It is such a huge process that I deeply feel like we shouldn't handle it on our own side to make it perfect as RevenueCat is a very well paid tool.

Please let me know in case there is an easier solution I missed.

from purchases-unity.

@melih-veloxia I agree with you that this is something that RevenueCat could and should handle.

We have it in our backlog, however I don't have an ETA.

In the meantime, the solution you described is as good as it gets, I'm afraid.

Hope that makes sense

from purchases-unity.

@aboedo Thanks for the update!

from purchases-unity.