Ignoring purchase request for already subscribed package error when trying to repurchase a consumable

Hi,

Happy to help here. Our SDK does consume all Android purchases by default, so this is unexpected. Can you confirm that you checked the “Multi-quanity” box in Google Play Console that allows the product to be purchased more than once?

Thanks!

Hi Ryan,

It wasn’t checked. But I have now checked it and tried again and it still comes back with the same error. Do I need to somehow reset it in Revenue Cat after making this change?

Hi @lawrence-e2e55c, sorry I was mistaken, that is specifically for multiple transactions/purchase event, not for multiple transactions across time.

Can you open a support ticket so we can get some more info/a screenshot of how the products are setup in Google Play Console?

Hi, I have exactly the same issue.

I am using Revenue Cat Paywalls to let my users purchase products. I have a subscription and a non-renewing consumable product set up. The consumable product is not linked to an entitlement. I can purchase it once, no issue. When I purchase it again, I get the error "Ignoring purchase request for already subscribed package”. I tested both options for the "multi quantity” box, with the same result.

Any updates for this issue?

I have raised a support ticket and its currently with Revenue Cat engineering. It’s been with them for a few weeks now with no solution yet. This is currently blocking my go live so its very frustrating.

I will update here if I find a solution. If you find a solution please let me know...

Further update, after a month I still have no update from the Revenue Cat engineering team which is quite frustrating.

However I have identified that this issue only affects Google Play and is not happening when I am testing on iOS using the simulator.

This was never resolved. I ended up writing my own paywall on Android… and I went live last weekend!

Any progress on this issue?  Should we expect to be fixed soon in some of the next releases or should we focus on building our own paywall as well? I think this is really big issue and affects the possibility to repurchase consumables, which leads to less 💸?

I found that on iOS there was no issue but on Android I still get the issue. I created a paywall for my consumables on Android. I still used the revenue cat functions to make the purchase for that paywall.

All my other paywalls, Android non-consumables and iOS paywalls, are using the revenue cat paywall functionality.

The replacement paywall took me 4 hours to develop which was much faster than waiting for a fix.

Lawrence, which paywall template did you use for consumables for iOS? None of them seem to be very good for consumables.. for me, I wanted a line item for each package with simply a name and a price, not the overly complicated two line subscription setup all existing paywalls seem to have. Any advice you could give would be greatly welcomed. I was thinking of setting up my own paywall for iOS but I am kind of lost as to where to start. I wanted to use the offerings with the experimental A/B testing, but I haven’t upgraded RevenueCat to even be able to look at that to see if it is worth paying for - I can’t tell if it will even work for consumables! Can you help me at all?

I have a similar issue with paywall dialogs, same error “

• Ignoring purchase request for already subscribed package

”

I get hit with that error when user tries to re-subscribe to a previously expired package.

Same issue showing - Ignoring purchase request for already subscribed package for a consumable product

Hey team, I’m raising this issue internally and will get back to you with an answer

​@MarcosC thank you!
I’m going to launch product with RevenuCat purchases and also noticed this issue with consumable product re-purchase
 

Ignoring purchase request for already subscribed package

We had a restriction to prevent purchasing it again. We have removed the restriction to custom packages https://github.com/RevenueCat/purchases-android/pull/2044 and should be released in Native this week and on the hybrids next week.

Be aware that Google might prevent you from purchasing a consumable if you haven’t consumed it.

> Before offering an item for sale, check that the user does not already own the item. If the user has a consumable that is still in their item library, they must consume the item before they can buy it again.

Docs: https://developer.android.com/google/play/billing/integrate

There is also a bug of revenuecat for consumable in Apple if we use revenuecat paywall - Suppose a user has consumable credit let say 50 coins already in his account and he buys subscription package [that gets 500 coins every month] the issue is when user buys subscription revenuecat sends 2 transactions one for subscription and another for credit, so, user is getting extra consumable credits for free [user is getting 550 credits if he buys subscription , it should get only 500 credits] - this issue only happens if we use revenuecat paywall.

Hi ​@adam-0aebea, RC doesn’t handle consumable tokens (e.g., coins) directly (see: https://www.revenuecat.com/docs/platform-resources/non-subscriptions). That means you must be updating the users’ balance in your backend—is it possible there’s a discrepancy in that logic?