When in-app purchase is requested for an already purchased non-consumable item the StoreKit first asks to confirm a new purchase and only after that finds the purchase and offers the item for free. To avoid this confusion my applications first tried to restore the purchase and if not found prompted for a new purchase. This approach didn't get complaints neither from end users nor from the Apple review team ... until recently.
When I submitted new releases of my apps, they were rejected by the review team who insisted that the app must have two buttons: one for Purchase, another for Restore.
Both application are designed in a way that makes adding a button to startup page completely undesirable. To reach a consensus, I decided that 'Purchase' button instead of immediately starting the process, should bring up an additional dialog to select 'Purchase', 'Restore' or 'Cancel'. This effectively creates two separate buttons and splits a single purchase process into two separate processes. Guess what: the application was rejected again!
I haven't got a chance to read the regulations (is there a way?), but have a strong feeling that the review team misunderstood them. To start with, I don't see a reason of having two separated buttons: it will be more logical to improve the StoreKit to avoid prompting for a purchase when it is already made. Secondly, I don't see why a separate dialog doesn't meet the regulations, given that it actually provides two separate buttons and splits the process.
Hopefully this forum will clarify the issue.
When I submitted new releases of my apps, they were rejected by the review team who insisted that the app must have two buttons: one for Purchase, another for Restore.
Both application are designed in a way that makes adding a button to startup page completely undesirable. To reach a consensus, I decided that 'Purchase' button instead of immediately starting the process, should bring up an additional dialog to select 'Purchase', 'Restore' or 'Cancel'. This effectively creates two separate buttons and splits a single purchase process into two separate processes. Guess what: the application was rejected again!
I haven't got a chance to read the regulations (is there a way?), but have a strong feeling that the review team misunderstood them. To start with, I don't see a reason of having two separated buttons: it will be more logical to improve the StoreKit to avoid prompting for a purchase when it is already made. Secondly, I don't see why a separate dialog doesn't meet the regulations, given that it actually provides two separate buttons and splits the process.
Hopefully this forum will clarify the issue.