Skip to main content
Solved

How can my merge my existing projects so they can chare subscriptions?

  • 10 December 2021
  • 4 replies
  • 247 views

Forum|alt.badge.img+4

Really exciting news about the new subscription sharing between apps feature.

I had already set this up using RevenueCat and some custom server and client side code to enable users to access their subscriptions across multiple apps.

Now that our apps have been auto migrated to projects, I’d like to have them all exist as one project with several apps. Is there a process to do this? In my specific case, I have 2x iOS and 1x macOS app, each with their own subscriptions at identical prices with my custom logic unlocking the entitlements across the apps when users sign in. It would be much easier to have RevenueCat handle this.

Thanks in advance!

Best answer by cody

Hey @JoeAllen!

I’d recommend just checking if the value exists- if no value exists when you fetch PurchaserInfo, then you can assume they’ve never had their receipt synced with this new app.

Additionally, syncPurchases is silent, and will return the new PurchaserInfo after syncing their transactions.

Does that make sense?

 

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

4 replies

cody
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 487 replies
  • December 10, 2021

Hey @JoeAllen!

We don’t have an automated process for this, but you should be able to follow the same steps for transferring apps between accounts and doing a client side migration here:

 

Basically, you’ll need to create new apps in your main project for your other apps. You’ll then want to configure the new apps to be the same as the projects you’re migrating from (don’t forget bundle ID, shared secret, entitlements/products, etc).

From the SDK, you’ll want to call syncPurchases on launch for apps launching the new version (with the new API key) so their receipt can be synced with the new app. You shouldn’t call this on launch every time, so make sure you are checking if the user actually exists in the new app first (on iOS, checking PurchaserInfo for originalApplicationVersion is a good way to see if a receipt has been synced).

Let me know if that helps!


Forum|alt.badge.img+4
  • Author
  • New Member
  • 2 replies
  • December 10, 2021

Thanks! To clarify, should I check that any value exists for originalApplicationVersion to verify that the user exists? Or should I validate that the version is (or isn’t) later than this particular update?


cody
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 487 replies
  • Answer
  • December 10, 2021

Hey @JoeAllen!

I’d recommend just checking if the value exists- if no value exists when you fetch PurchaserInfo, then you can assume they’ve never had their receipt synced with this new app.

Additionally, syncPurchases is silent, and will return the new PurchaserInfo after syncing their transactions.

Does that make sense?

 


Forum|alt.badge.img+4
  • Author
  • New Member
  • 2 replies
  • December 10, 2021

Yes that makes perfect sense thank you!


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