Skip to main content
Question

Issue with ProductAlreadyPurchasedError & RECEIPT_ALREADY_IN_USE Flow.

  • November 9, 2025
  • 2 replies
  • 33 views

Forum|alt.badge.img+2

I have configured “Keep with original App User ID” as transfer behaviour which leads to binding of a subscription to a single userID.

Now lets say user has bought the subscription while being logged into accountA, later at some point user uninstalls the app and logins with accountB in app, now playstore being the same, when user tries to subscribe again, the error will come: Product Already Purchased Error

Upon triggering Purchases.restore or Purchases.sync, we will get RECEIPT_ALREADY_IN_USE, I want to show the user accountA details so user can log back in with correct account, however I can’t as revenue cat doesnt surface any usable info in above errors, like appUserId / receipt / token of the purchase from the previous account which I can query in my backend to fetch accountA details.

What is the correct way here ?

This post has been closed for comments

2 replies

chris_perriam
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • November 14, 2025

Instead of the “Keep with original App User ID” option, I’d recommend the Transfer if there are no active subscriptions option. This will allow the receipt to transfer between users, but only if the user does not have an active subscription.

If you wish to find the App User ID a subscription is associated with, you can use our Search subscriptions by store subscription identifier API from your backend server. This will return the RevenueCat App User ID associated with a given Play Store Order ID.

To find the Order ID for the logged-in Play Store account’s subscription, you’d first need to query the Google Play Billing Client for the purchase token within your app. Then you’d need to resolve this purchase token to an Order ID using the Google Play subscriptions API on your backend server.

I’ll share your use-case with our team. This isn’t a common request, but I do recognize this flow isn’t easy to support currently. Let me know if there’s anything I can clarify - happy to help!


Forum|alt.badge.img+2
  • Author
  • New Member
  • November 15, 2025

Yes I did something along above lines for the app in the meantime, would appreciate highlighting the use case to the team, if it gets easier to support in future, would be great!
Thanks.

best,

Shabinder