In-App Purchase Programming Guide - Apple Developer

Preparing for App Review
Implementation Checklist
During development, you run a development-signed version of your app, which connects to your development
servers and the test environment for the App Store. In production, your users run a production-signed version
of your app which connects to your production servers and the production App Store. However, during app
review, your app runs in a mixed production/test environment: it’s production signed and connects to your
production servers, but it connects to the test environment for the App Store.
When validating receipts on your server, your server needs to be able to handle a production-signed app
getting its receipts from Apple’s test environment. The recommended approach is for your production server
to always validate receipts against the production App Store first. If validation fails with the error code “Sandbox
receipt used in production”, validate against the test environment instead.
Implementation Checklist
Before you submit your app for review, verify that you’ve implemented all of the required behavior. Make sure
you’ve implemented the following core In-App Purchase behavior (listed in order of a typical development
process):
●
Create and configure products in iTunes Connect.
You can change your products throughout the process, but you need at least one product configured
before you can test any code.
●
●
Get a list of product identifiers, either from the app bundle or your own server. Send that list to the App
Store using an instance of SKProductsRequest.
Implement a user interface for your app’s store, using the instances of SKProduct returned by the App
Store. Start with a simple inteface during development, such as a table view or a few buttons.
Implement a final user interface for your app’s store at whatever point makes sense in your development
process.
●
●
Request payment by adding an instance of SKPayment to the transaction queue using the addPayment:
method of SKPaymentQueue.
Implement a transaction queue observer, starting with the paymentQueue:updatedTransactions:
method.
Implement the other methods in the SKPaymentTransactionObserver protocol at whatever point
makes sense in your development process.
●
Deliver the purchased product by making a persistent record of the purchase for future launches,
downloading any associated content, and finally calling the finishTransaction: method of
SKPaymentQueue.
2013-10-22 | Copyright © 2013 Apple Inc. All Rights Reserved.
42