EntitlementInfo is null.

Imagine this is related. When I try to restore purchases...

Error consuming purchase. Will retry next queryPurchases. DebugMessage: Item is not owned by the user.. ErrorCode: ITEM_NOT_OWNED.

Also, after each purchase is completed it’s getting consumed immediately (Consuming purchase with token ...), and I can purchase the item again. Which I think is expected behaviour before an app is live on an app store?

Could this explain why there is no entitlement?

If that’s the case, how do I test for entitlements?

Hi ​@Mr Qwak, thanks for posting. It might be best to reach out to support, as we can dig into your configuration and logs and see what’s happening. Also, I’m sure you’ve already configured this, but I wanted to double-check that you’ve created an Entitlement and attached your products to it.

Regarding the “item not owned by the user” issue, can you review your restore/transfer behavior and let us know if you’ve chosen any option other than the default (“Transfer to new App User ID”)?

Thanks for your response Jeffrey.

Yeah, there were a few things I was struggling to get to grips with, and I was also confusing Entitlement ‘Identifier’ with ‘RevenueCat Entitlement ID‘.

I’m making progress now. Will reach out to your support if need be.

There are only non-consumable IAP’s in my Android app, and one thing that I’m still not sure of; if a customer requests a refund with Google, does revenue cat monitor and reflect the change in it’s Entitlements? If so, how long does it take for the Entitlement to update?

Thanks again.

​@Mr Qwak You’re welcome! As long as you’ve integrated Google Real-Time Developer Notifications, we should update entitlements as soon as we receive the updated information from Google.