Skip to main content
Solved

Creating purchase with same purchase token not creating alias

  • 21 October 2021
  • 1 reply
  • 45 views

Forum|alt.badge.img+4

I'm experiencing an issue with automatic aliasing for user ids.  I have migrated some user purchases from Stripe and Android but in my upload script I used a capitalised UUID instead of lower case (which is what my mobile app uses).  I didnt release RevenueCat uses case sensitive user ids.

When I try to submit the purchase again with lower case UUID using the same purchase token, a new customer is created (as expected) and the purchase is transferred to the new customer (not expected).  I thought based on your documentation these two user ids would be aliased and they would share the purchase, but it seems they aren't. 

 

I've made sure to add the "is_restore": "true" flag when uploading via your /receipt REST endpoint.

 

Can you advise why this isnt working as expected and what I can do to fix?

Best answer by James N

Hi - for anyone else experiencing this issue, I found the answer here:

https://docs.revenuecat.com/docs/user-ids

Automatic aliasing seems to only occur if user_ids are not App Provided ids (e.g. they are anonymous ids).  In my case, the current behaviour is expected.

 

Cheers
James

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

Forum|alt.badge.img+4
  • Helper
  • October 21, 2021

Hi - for anyone else experiencing this issue, I found the answer here:

https://docs.revenuecat.com/docs/user-ids

Automatic aliasing seems to only occur if user_ids are not App Provided ids (e.g. they are anonymous ids).  In my case, the current behaviour is expected.

 

Cheers
James


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