Databases
StackOverflow2013
Postsdbo
PORestoring In-App Purchase Transactions
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORestoring In-App Purchase Transactions
    primarykey
    data
    text
    <p>The idea is whether rain or shine, wet or fine, user must get that he paid for all out.</p> <p>From Apple:</p> <pre> Store Kit provides built-in functionality to restore transactions for non-consumable products, auto-renewable subscriptions and free subscriptions </pre> <p>For these transactions Apple Store Kit has good build-in tools. I want to focus on other types (consumable in particular). One and only transaction information is an identifier and a receipt data which we receiving by Store Kit after successful purchase. Our application uses server-side model to deliver products to it. But there still much cases of losing purchase data, such as if the server lay down while user is making purchase via App Store so its not possible to send receipt to server to complete verification process.</p> <p>Current workaround is:</p> <ol> <li>Server returns a list of product identifiers</li> <li>User selects one; app saves its identifier on device (via SQLite or Core Data). Standart Apple Store transaction process goes right after that.</li> <li>In case of success application saves receipt data in conjunction with its identifier on device and send it to server. If there were failure or cancelation the identifier is immediatelly removed from device.</li> <li>If server's response is OK then app removes identifier with receipt data from device. Otherwise it will send requests to server periodically until successful response behaves.</li> </ol> <p>But this approach still has leaks. For example, user can remove application from device not waiting for transaction delivering to server, so there will not any proof about his purchase at all.</p> <p>Your suggestions?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmnel
    1. USLion
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORestoring In-App Purchase Transactions
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORestoring In-App Purchase Transactions
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORestoring In-App Purchase Transactions
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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