Reputation: 9491
I have a multiplatform app (Android, iOS, Windows) and implemented one license for the app. I have a webserver to make the license available across all the platforms. I use consumable in-apps to implement it. License is bought, added to a webserver and consumed. It's consumable because it should be added to a webserver only once. Everything was fine until now. (1.5 years since initial iOS release) Now my app got rejected. According to the apple I use incorrect in-app type. (I disputed that I have multiplatform app but they keep rejecting my app) But I do not understand what for do I need to use non-consumable in-app to make it comply to their guidelines. Any ideas what I did incorrectly and how to fix it? Should I completely remake licensing in my app?
Upvotes: 0
Views: 407
Reputation: 9491
I had a phone call with Apple and they explained what they require:
PS: The idea with subscription sounds easier to implement and I decided to switch our licensing to non-renewable subscriptions as @Paulw11 suggested. The only disadvantage is that subscription must be time limited. So, I will have one year subscription.
Upvotes: 0
Reputation: 5169
They may be rejecting your app since users will have no way to restore their license if they reinstall the app, get a new phone, etc. Non-consumable purchases are permanently appended to the users Apple receipt file so they can be "restored" even years after they were purchased.
The other way to offer restore functionality is if you require all users to login with app specific accounts, where you can restore any purchases directly from your server.
Usually app review provides a rejection reason and violated guidelines. Anything here?
Upvotes: 1