Skip to main content

Hello,

I would greatly appreciate it if you could provide guidance on transitioning from Glassfy.

Background:

  • iOS app only
  • Capacitor framework
  • Currently, the App Store version uses Glassfy.
  • I have a fully prepared version that supports both RevenueCat and Glassfy (I can choose which module to use).

I've outlined a few points below. Could you please confirm if my understanding is correct for each of them?

  1. Can I, without releasing a new version, configure App Store Connect to send data to RevenueCat, and set up a redirect from RevenueCat to Glassfy? Would this work, with new purchase data being duplicated in both services?

  2. In parallel, I plan to request a data export from Glassfy and use your API to import this data into RevenueCat.

  3. Once that's done, I should be able to release my new version, which can theoretically drop Glassfy support entirely and rely solely on RevenueCat.

  4. Users who make purchases in the time between my CSV import and the release of the new version will need to manually tap "Restore Purchases." Alternatively, can I automate this by calling the syncPurchases function for them?

  5. Can I always call syncPurchases for all users when the app is launched, to ensure everyone is synchronized with RevenueCat? From what I understand, this takes some time. If this is recommended, how can I determine the right time to trigger this? Should I set a flag in my backend or is there a smarter approach?

Thank you very much for your help!
 

@MarcosC  You responded in a similar thread, so perhaps you could also check if everything is okay with my plan here?

Hey 👋

 

Thanks for pinging me 😃 . Let me try to go through your questions

  1. Can I, without releasing a new version, configure App Store Connect to send data to RevenueCat, and set up a redirect from RevenueCat to Glassfy? Would this work, with new purchase data being duplicated in both services?

Yes, this is probably one of the first things you need to do. By default, we ignore notification for purchases we don’t have in our system. If you’d like us to track that purchase, check this → https://www.revenuecat.com/docs/platform-resources/server-notifications/apple-server-notifications#tracking-new-purchases-using-apple-app-store-server-notifications

  1. In parallel, I plan to request a data export from Glassfy and use your API to import this data into RevenueCat.

Great. If you get this and need to import them, open a support ticket, include the csv and tell them that I told you to do that 😃 - and I can run the import.

  1. Once that's done, I should be able to release my new version, which can theoretically drop Glassfy support entirely and rely solely on RevenueCat.

Yes, though if customers don’t upgrade, they would be still purchase using Glassify. You have to alternatives for this. (a) configure what I mentioned in 1. (b) do nothing and the user when they upgrade would need to restore purchases 

  1. Users who make purchases in the time between my CSV import and the release of the new version will need to manually tap "Restore Purchases." Alternatively, can I automate this by calling the syncPurchases function for them?

Yes, just don’t spam syncPurchases as it might cause undesired transfers. I would just call syncPurchases for those that upgraded. An alternative is what I described before

  1. Can I always call syncPurchases for all users when the app is launched, to ensure everyone is synchronized with RevenueCat? From what I understand, this takes some time. If this is recommended, how can I determine the right time to trigger this? Should I set a flag in my backend or is there a smarter approach?

There was a thread in community about tracking this on device. syncPurchases makes a restore. Depending on your app, it could be transferring purchases between users

 

Hope this helps 🙂 - Ping me if not

Terms & ConditionsCookie settings