Skip to main content
Question

Revenuecat E/[Purchases] - ERROR( 7251) ErrorCode: DEVELOPER_ERROR.DebugMessage: Account identifiers don't match the previous subscription..

  • March 29, 2025
  • 1 reply
  • 11 views

Forum|alt.badge.img

When I try to pay for a subscription in the app, and then I cancel the subscription.
When I log out of the account and switch to a new account, and want to retest the paid subscription function, the following error is displayed.


And the terminal shows those error:  

 πŸ€–β€Ό BillingWrapper purchases failed to update: DebugMessage: Account identifiers don't match the previous subscription.. ErrorCode:: DEVELOPER_ERROR.null
E/[Purchases] - ERROR( 7251): πŸ€–β€Ό PurchasesError(code=PurchaseInvalidError, underlyingErrorMessage=Error updating purchases. DebugMessage: Account identifiers doon't match the previous subscription.. ErrorCode: DEVELOPER_ERROR., message='One or more of the arguments provided are invalid.')

And no matter which account I switch to, the same token is used when creating an order? In other words, when using this app, the user's Google Play account will be bound to the first paid account by default. After that, no matter which account this app switches to, an error message will be displayed when clicking on the payment?

 

Is there a good solution to keep each account independent? Even if I switch between different accounts in the app, I can still pay for the subscription product?

I tried clearing the cache of the Google Play Store, but it didn't seem to work.

1 reply

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 277 replies
  • April 2, 2025

Hi ​@packy. On both Google and Apple devices, purchases are associated (on a single receipt) with the  underlying Google Account / Apple ID that the device is logged into. Unfortunately, this is a fundamental limitation of both the Play Store and App Store, and it’s not possible for multiple users of your app to share a single device and each have their own subscriptions. 

We have several different restore/transfer behaviors that you may want to review, as they can transfer or prevent purchase transfers between app users.

Also, we have a mechanism of granting entitlements (outside of the stores), which you might find helpful if you’re trying to set up a family / multi-user flow. Let me know if you have additional questions!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings