I know if you plan to call restoreCompletedTransactions, then when the user presses the button, whether it should be called automatically or manually is a problem ( For example, see here).
My question is whether it is necessary to call restoreCompletedTransactions. If my app has only one or two things to sell/unlock, then it seems okay to let users buy through the standard user interface Accepted, as long as there is a note explaining that if they buy something they will not charge the user again for the purchase. So, suppose the user installs my game on a new device. On their old device, they have already purchased/unlocked Class X. When they reach the Class X of the new device, it asks if they want to buy it (explaining that they won’t be charged twice if they buy them before), and they say yes, they are now in their new device. There is an X grade on the device, and they only charge once (when they buy it on an old device).
As far as Apple’s approval is concerned, is this a kosher way of handling it? I can see that if they have purchased 100 individual items, it would be good to restore them all at once. But if the entire application is unlocked only once or twice, is my no-restoreCompletedTransactions method acceptable?
The reason is that calling restore will display the authentication window, which is not considered a good user experience.
I hope to use iCloud to solve it in iOS 5. This problem is solved.
When selling non-consumables through in-app purchases on iOS, the restoreCompletedTransactions method is provided so that you can retrieve all the purchases made by the user in the past, according to I understand this is to provide users with a quick way to restore purchases, such as when they get a new device.
I know if you plan to call restoreCompletedTransactions, then when the user presses the button, should it be automatic Or calling it manually is a problem (see here for example).
My question is whether it is necessary to call restoreCompletedTransactions. If my app only has one or two things to sell/unlock, then let the user Purchasing through the standard user interface seems acceptable, as long as there is a note explaining that if they buy something from them, the user will not be charged again for the purchase. So, suppose the user installs my game on a new device. On their old device , They have purchased/unlocked the X level. When they reach the X level of the new device, it asks if they want to buy it (explaining that if they bought them before, they will not be charged twice), and they said Yes, they now have Class X on their new device, and they only charge once (when they buy it on the old device).
As far as Apple’s approval is concerned, this is a way to deal with it The Jewish way? I can see that if they have purchased 100 individual items, it would be good to restore them all at once. But if the entire application is unlocked only once or twice, is my no-restoreCompletedTransactions method acceptable?
Restore should only be performed under the user’s operation. You can have a button called Restore Previous Purchases.
The reason is that calling restore will display the authentication window, which is not considered a good user experience.
I hope that in iOS 5, using iCloud will solve this problem.