Skip to main content
Solved

Paid app with in-app upgrades, how to get the initial purchase date


Forum|alt.badge.img+1

I am developing an app that gives access to a certain database for information lookup.

The idea is to charge $2.99 for the app in the app store which gives access to the current version of the database for life.

Then, whenever a new version of the database is available (happens annually), offer a non-consumable in-app purchase to get lifetime access to the new version.

My problem

If a user buys the app in 2022 and uninstalls it when the in-app offer to upgrade to 2023 comes up (not purchasing the upgrade) and then reinstalls it, How can I figure out what version of the database they are entitled to? 

How can I determine when they first bought the app?

Best answer by cody

Hey @kojoman!

You can determine the first date of download/purchase by the originalPurchaseDate property on CustomerInfo: https://docs.revenuecat.com/docs/purchaserinfo#get-user-information

Note: this property is only valid on iOS after a user has had their receipt synced with RevenueCat.

View original
Did this post help you find an answer to your question?
This post has been closed for comments

cody
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • May 20, 2022

Hey @kojoman!

You can determine the first date of download/purchase by the originalPurchaseDate property on CustomerInfo: https://docs.revenuecat.com/docs/purchaserinfo#get-user-information

Note: this property is only valid on iOS after a user has had their receipt synced with RevenueCat.


ryan
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • May 23, 2022

Another option here could be to set up an Entitlement in RevenueCat for each database year along with a new product in App Store Connect. Every year you’d release a new non-consumable product and Entitlement. 


Forum|alt.badge.img+1
  • New Member
  • May 26, 2022

Thanks 🙏 


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