Note that there are some explanatory texts on larger screens.

plurals
  1. POGet Customer Information from an In App Purchase transaction on iPhone
    primarykey
    data
    text
    <p>Apple clearly states in their <strong>Introducing Store Kit</strong> video in the iPhone Dev Center that we should: </p> <blockquote> <p><em>"Keep a copy of the <strong>TransactionID</strong> along with the <strong>Customer Information</strong> in your server in the cloud. This way if the customer mistakenly deletes your application, you have a mechanism for recovery. You can check your server on first launch of your app for a record of the purchases for a given customer and bring that app back to its state before it was deleted. Believe me your customers will be thankful!"</em></p> </blockquote> <p>Great! Now, I haven't worked with In App Purchasing yet but in looking over the <a href="http://developer.apple.com/iphone/library/documentation/NetworkingInternet/Conceptual/StoreKitGuide/index.html" rel="nofollow noreferrer">In App Purchase Programming Guide</a> it's not apparent how or when Store Kit makes available any "Customer Information" to the app. So, my guess is we need to trouble our customers for this information, regardless of whether we use In App Purchasing or not, given that Apple doesn't give us any access to the vCard in their Address Book that contains this valuable information.</p> <p>Are my assumptions correct? In order to be able to restore from the deletion of an app after an In App purchase we'd need to get some type of unique info from each user to log on our servers during each purchase?</p> <p><em>Edit: We would be considering the Built-In Product Model with In App Purchases.</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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