Skip to main content
Solved

Android users have to restore purchase after updating the app


Forum|alt.badge.img+7

We’ve just issued an update to our app yesterday.

We’re getting support requests every hour from customers who were on a subscription or free trial. Their subscription is not applied to the app after the update, so they are angry and think we’ve taken their subscription away!

To fix it, we just ask them to do a restore purchases. Works every time.

Can anyone think why this is happening?

What can we do to fix it so we don’t get hammered on support?

Best answer by ryan

You can call `.createAlias()` and pass a new ID which will merge the identities together and treat them as the same customer going forward. This cannot be undone, so it’s worth triple checking the ID is being set to the expected value and never null or a hardcoded string.

View original
Did this post help you find an answer to your question?

4 replies

ryan
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • 391 replies
  • October 5, 2021

It sounds like your update may have cleared out or changed the App User ID? Calling .reset() or .logout() would clear it out, or you may be calling .identify() or .logIn() with a different App User ID from before the update?

If you go to one of the Customer timelines in RevenueCat of someone who successfully restored do you see an event that an alias was created or the purchases were transferred from another customer? That would indicate that the App User ID was changed at some point.


Forum|alt.badge.img+7
  • Author
  • Active Member
  • 11 replies
  • October 5, 2021

Thanks @ryan, ah yes that is happening. Is there a way we can give them a new ID without clearing the purchases?


ryan
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • 391 replies
  • Answer
  • October 5, 2021

You can call `.createAlias()` and pass a new ID which will merge the identities together and treat them as the same customer going forward. This cannot be undone, so it’s worth triple checking the ID is being set to the expected value and never null or a hardcoded string.


Forum|alt.badge.img+7
  • Author
  • Active Member
  • 11 replies
  • October 6, 2021

Many thanks for this, really appreciated! 

 

We’ve given it a go and sent a build to Google. We also made extra sure the ID is the one we want :thumbsup_tone2:


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