Databases
StackOverflow2013
Postsdbo
POswitching from auto-renewable to renewable subscription
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POswitching from auto-renewable to renewable subscription
    text
    copied!<p>My client has an app in the App Store that uses the auto-renew subscription type. Upon resubmitting the app it was rejected because they claimed they don't have periodic content (even though they do... but this problem seems to be ubiquitous currently). I was wondering what the best approach is to deal with non-renewing subscriptions. Specifically issues dealing with:</p> <ol> <li>Losing your device and restoring your subscription</li> <li>Restoring your subscription to multiple devices (as mandated by Apple)</li> <li>Preventing users from abusing the system.</li> </ol> <p>What I came up with so far is the following:</p> <p>When a user purchases a 1 month subscription this information is stored locally (say in NSUserDefaults). Also, a unique ID is generated and sent to my clients server. When the subscription ends users are asked whether they want to be directed to the purchase screen. If users wishes to save the subscription in case they need to restore they device, or in case they lose their device, they can opt to have the unique identifier sent to their email address (which they are prompted to enter, indicating that this information will not be used). The app has an place to enter this ID. It will retrieve the subscription information from the server and again store this in the NSUserDefaults. Each time a restore is done, a counter is increased. When it has reached say 5, the user can no longer restore. The same principle described above works in the case of sharing subscriptions over multiple devices. Does this seem like a reasonable solution (and one that Apple will accept)?</p> <p>Thanks for your time!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload