I currently have two RevenueCat projects, one containing an older version of my iOS app, and one containing Android. I’m currently working on an iOS update, and I’d like to amalgamate both of these apps into one project, but I can’t see how to do this. I can set up a new iOS app in the same project as the Android one, which means that all new subscribers will end up there, but is there some way of moving existing subscribers?
Solved
Transferring subscription to a different project
+6Best answer by kaitlin
Hi
Yes, in order to get both of these apps into one project, you will need to set up a new iOS app in the project that holds the existing Android app (or vice versa).
I’d recommend following these steps:
- in the new iOS app (app #2), set up your existing bundle id, credentials, products, entitlements and offerings from app #1
- change the public API key in your app’s code to the one matching your new iOS app (app #2)
-
add client-side migration code to the app (basically, if the user is subscribed to app #1 and not subscribed to app #2, sync purchases)
-
ship an update with the migration code and the new API key
This should ensure that your users won’t experience any disruption, and over-time all of your users and purchases will be migrated from app #1 to app #2.
+6Hi
Yes, in order to get both of these apps into one project, you will need to set up a new iOS app in the project that holds the existing Android app (or vice versa).
I’d recommend following these steps:
- in the new iOS app (app #2), set up your existing bundle id, credentials, products, entitlements and offerings from app #1
- change the public API key in your app’s code to the one matching your new iOS app (app #2)
-
add client-side migration code to the app (basically, if the user is subscribed to app #1 and not subscribed to app #2, sync purchases)
-
ship an update with the migration code and the new API key
This should ensure that your users won’t experience any disruption, and over-time all of your users and purchases will be migrated from app #1 to app #2.
+6Thanks for your reply. If I understand correctly from looking at the client-side migration code, what I’d need to do is:
- Check whether they have a subscription registered in the new RC app
- If not, check whether they have a subscription in the old RC app
- If so, migrate the old subscription to the new one.
This makes sense, but I’m not quite sure how to do step 2. Would I have to call
Purchases.configure(withAPIKey: ‘oldAPIKey’)to configure my client to use old RC app so I can check the subscriptions there?
Thanks,
Owen
+6Hi
I wouldn’t recommend configuring with the old API key - what you could do is make an API call to the GET /subscribers endpoint using your old key and check their customerInfo there: https://www.revenuecat.com/docs/api-v1#tag/customers/operation/subscribers
Then, continue with the same logic - if their entitlement isn’t empty in the customerInfo from your previous app, sync their purchases in your new app.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.