CODEWITHSUNDEEP
swiftin-app-purchase
fs_tigre
fs_tigre

Reputation: 10738

What is the recommended logic to use when checking authenticity in Auto Renewal Subscriptions

I have an app where I’m offering Auto Renewal Subscriptions. Here is how it currently works, when the user subscribes, it saves a Bool in UserDefaults as true, after that I can make a receipt request to see if the subscription has expired. My issue or what I don’t fully understand is the logic on how often to make that request, checking for authenticity every time the user launches the app seems like a lot, or do I need to save the expiration date in UserDefaults and just check a couple of days after the expiration date to see if the user renewed? This way we limit the requests we make to retrieve the Apple receipt.

Can someone share the logic used when checking for authenticity in an app using Auto Renewal Subscriptions?

Upvotes: 1

Views: 98

Answers (1)

enc_life
enc_life

Reputation: 5169

The "right" way to do it is to manage everything server side (with some caching on the device in case the user is offline). Refreshing the receipt on the device is insecure, slow, and could make that annoying "Login with iTunes" prompt keep popping up for the user :)

It also prevents you from ever having complete analytics of your subscriber base since you can only get data points when they are active in the app.

What you would do is store the receipt file in a database after purchase, and refresh it there to keep the subscription status up-to-date. Then your app is asking your database if the user is subscribed (and caching the value in UserDefaults).

Here is a good blog post that outlines what the setup should look like: iOS Subscriptions are Hard

Upvotes: 2

Related Questions