Restore Purchase not working after updating to 9.1.1 in Android

[mehul4795]

I have been using the RevenutCat SDK for more than 2 years in my Android app. After upgrading the RevenueCat Android SDK from 8.x.x to 9.1.1, the restore purchase functionality has stoped working in my app and many of the users are complaining regarding the same. After upgrading the SDK version, I haven't made any code changes in the Restore Purchase functionality.

You can find the code that I am using below.

fun restorePurchase(): Flow<PlanPurchaseState> {
        return callbackFlow {
            trySend(PlanPurchaseState.PurchaseInProgress)

            Purchases.sharedInstance.restorePurchasesWith(onError = { error: PurchasesError ->
                trySend(PlanPurchaseState.PurchaseError(error.message))
                close()
            }, onSuccess = { customerInfo ->
                val entitlementInfo =
                    customerInfo.entitlements.all.values.firstOrNull { it.isActive }

                if (entitlementInfo == null) { // No previous purchase found
                    trySend(PlanPurchaseState.PurchaseError(context.getString(R.string.premium_plans_error_no_earlier_purchases)))
                } else {          
                    trySend(PlanPurchaseState.PurchaseSuccess(currentActivePlan))
                }

                close()
            })

            // Waits for the function to get finished and is only called after the close() function is invoked
            awaitClose()
        }
    }

When the above code is executed, I am getting entitlementInfo null every time even though a purchase was made earlier. Any help will be appreciated.

1. Platform: Android
2. SDK version: 9.1.1
3. OS version: Android 16
4. Android Studio version: Narhwal 2025.1.1 Patch 1
5. How widespread is the issue. 100% devices affected.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[MarkVillacampa]

Hi @mehul4795,

Are you perhaps using anonymous users and expired transactions or consumed one-time products?

There is a limitation in Billing Library 8 which our SDK v9 integrates:

Play Billing Library 8 removed functionality to query expired subscriptions or consumed one-time products. This means that, for users migrating from a non-RevenueCat implementation of the Play Billing Library, the SDK will not be able to send purchase information from these purchases. We can still ingest historical data from these purchases through a backend historical import. See docs. This doesn't affect developers that have all transactions in RevenueCat, which is true for the vast majority.

https://github.com/RevenueCat/purchases-android/releases/tag/9.0.0

Is this is your case your best option right now is downgrading to an SDK version v8 which uses Billing Library 7.

If this is not your case and you're still having problems, feel free to email me mark (at) revenuecat dot com with your project details and I'll take a look.

[mehul4795]

I am using consumed one time purchase using anonymous users. But as you quoted

This doesn't affect developers that have all transactions in RevenueCat, which is true for the vast majority.

We have all of our transactions in RevenueCat. So as per my understanding, my app should not be affected by this change 🤔

[fanwgwg]

+1 Seeing the exact same issue. Made a huge mistake by upgrading to V9 as we also have all our transactions in RC, so I thought we were not affected by the limitations as mentioned above. Now all anonymous users cannot restore their consumed one time purchases.

[mawr92]

Hey @fanwgwg,

Sorry to hear you're affected by this!

As Mark mentioned in his previous comment, the best option right now is to downgrade to SDK version v8, which uses Billing Library 7.

[mehul4795]

@mawr92 Thanks for the reply. Will the fix be included in the upcoming updates? If yes, any eta for the same?

[mawr92]

@mehul4795, yes, the team is working on a workaround for this! I don't have an ETA at the moment, but we will keep you posted!

[mehul4795]

@mawr92 Thank you 👍

[mehul4795]

@mawr92 I just saw that an update with version 9.3.0 was published. Does it fix the issue?

[ssand]

@mawr92 any updates on this issue? Judging by the v9.3.0 change logs it doesn't seem to be addressed.

[mawr92]

Hey @mehul4795, @ssand,

Thank you for following up and for your patience! 🙌 The team is still working on a workaround for this issue. We will let you know as soon as this gets released!

[tonidero]

Hi everyone! I wanted to give a summary and update on this issue.

Currently on major 9 of the RevenueCat Android SDK, which uses Google's Billing Client 8, it's impossible to obtain any consumed one time purchases from Google since they removed the methods to query for historical purchases.

Unfortunately, this means that the mechanisms we used to use to be able to restore these consumed purchases don't work anymore, and we can't securely know that the user purchased one of those products before. For developers using their own account system, they should be able to rely on that to recover purchases, by just having the customer log in. For those using anonymous users however, the situation is trickier since there is no such recovery system.

For these cases, we're currently testing with some backup functionality that Google provides, like Auto Backup and Block store, and we have a working prototype in the works. This option is not perfect however, since these backups don't work that well when a customer uses multiple devices simultaneously, but should limit the spread of this issue, by being able to restore a backup of the device in a different device, effectively recovering the anonymous user ids in some scenarios which would in turn recover these purchases. We plan to launch new versions in both major 8 and 9 with these changes.

We're still researching for other options we could use to recover these consumed purchases. In the meantime, we would suggest for all developers to:

1. Review your product configuration and make sure that any products that should be purchased only once per customer are configured as non-consumables in the RevenueCat dashboard. This would avoid us from consuming these purchases, completely avoiding this problem. This won't fix purchases that have already been consumed though.

2. If you are in this situation, that is, you use anonymous users and have products consumed that need to be recovered, please stay in major 8 of our SDK, which still allows to query for historical purchases. Do make sure to follow step 1 to avoid this issue from spreading more in the future though.

Thank you for your patience while we try to figure out the best path forward.

[hanks-zyh]

I hava same issue when updating to Revenuecat SDK 9.x.

1. I use revenuecat SDK since 2022 year.
2. I had config the product type as non-consumable.

But the user can't restore the pruchase on SDK 9.X still even thought the user pruchase the product on 2025/7/12 by Revenuecat SDK

What should I do to avoid this issue from spreading more in the future though? I would like to provider some purchase order info if you want.

[tonidero]

Hi @hanks-zyh, could you contact us with your app and product identifier? We would like to check the configuration for your products.

One theory is that, we run a migration on August 6th that, by checking if the product was attached to a lifetime package and behaved like a non-consumable, converted some products configured as consumables to non-consumables, in order to fix this issue for these products. We believe your product might have been part of this script run. If this is the case, all purchases done before Aug 6th would have been consumed, and any after would remain unconsumed.

[hanks-zyh]

Hi @hanks-zyh, could you contact us with your app and product identifier? We would like to check the configuration for your products.

One theory is that, we run a migration on August 6th that, by checking if the product was attached to a lifetime package and behaved like a non-consumable, converted some products configured as consumables to non-consumables, in order to fix this issue for these products. We believe your product might have been part of this script run. If this is the case, all purchases done before Aug 6th would have been consumed, and any after would remain unconsumed.

Thanks for reply, I hava send the infomation of product in RevenueCat Help center just now, please check it.