IOS Internal purchase implementation and test Check List

IOS Internal purchase implementation and test Check List

The free + in-APP purchase model has proved to be the most effective profit model. Therefore, implementing the in-APP purchase function may be a required task and skill for many developers. However, given that the inner purchase is not a small pitfall, And because sandbox testing requires a lot of specific configurations, developers with less experience can easily encounter various problems, an error occurred during the test. Apple only provided valuable error messages such as "Can not connect iTunes Store" or "Invalid Product IDs" without detailed error descriptions, therefore, debugging usually has no direction. Some of my predecessors have compiled a relatively complete check list here, but the content is different from the current situation because it is a little older. Taking advantage of the new problems encountered in the internal purchase in the last two projects, a relatively new Chinese Check list is summarized on this basis, hoping to help later users.

If you encounter problems when implementing and testing iOS app purchases, you can compare the items listed below one by one and check them one by one. I believe most of the errors can be ruled out. If your problem is not in the scope of this list, please note in the comments that I will update it.

• Whether you have enabled the AppIDIn-App PurchasesFunction? Log on to the Certificates of iOS Dev Center, and find the App being developed under Identifiers & Profiles In Identifiers. The In-App Purchase item should show Enabled if Xcode5 is used, you can directly open In-App Purchases on the Capabilities page of Xcode ).
• Have you registered your IAP project in iTunes Connect and set it to Cleared for Sale?
• In your plistBundle identifierIs the content consistent with your AppID?
• Are you sure you have entered VersionCFBundleVersion) and BuildCFBuildNumber? Both are indispensable.
• When you use the code to apply for an item list from Apple, do you use the complete Product ID registered in iTC? Use the string in the Product ID column of the purchased item in IAP Management)
• Have you re-generated the provisioning profile that includes the IAP license after enabling IAP?
• Have you re-imported the new provisioning profile containing IAP? We recommend that you delete the old provisioning profile on the original device in Organizer.
• Are you using provisioning profile containing IAP to deploy the test program? In Xcode5, we recommend that you use the Team option in General for automatic management.
• Are you testing IAP in the simulator? In theory, although the simulator can test the IAP in some cases, many conditions are not reassuring. Therefore, you do need a real machine to test the IAP.
• Are you testing IAP in Enterprise Edition Release? Because the Enterprise Edition does not have an iTC for internal purchase project management, and you cannot publish an AppStore application, you cannot use IAP in the enterprise build.
• Have you deleted the original app on the device and re-installed it? Remember to make Clean and Clean Build Folder before installation.
• Did you log out the actual Apple ID on the device before running the application? We recommend that you log out the Apple ID in use in Settings> iTunes Store and App Stroe, and enter the application for testing without logon.
• Are you using Test User? If you have not created a Test User, you need to create it in iTC.
• Is your test account an account in the US region? Although it is not necessary, we strongly recommend that you use the account in the U.S. region because the testing accounts in other regions are often exhausted and the account in the U.S. region has been stable. Under normal circumstances, IAP does not need to bind a credit card or fill in other information. If this happens, you can try to delete this test account and create another region.
• Have you created a new account for testing? If possible, try creating a test account, because the test account will be locked by Apple in certain circumstances.
• Is your application Rejected (Rejected) or Developer Rejected? Applications in the rejected status will also be rejected for inner-purchased items that have not passed. Therefore, you need to set the IAP project to Cleared for Sale again.
• Is your application waiting for the Developer to Release Pending Developer Release? IAP waiting for release status cannot be tested.
• Have you created or changed your in-house purchase project recently? It may take some time for an in-house purchase project to respond to all servers. This process is generally an hour or two, and it may take several hours.
• Are there any projects in the Contracts, Tax, and Banking Information project in iTC that have not been set or have expired? Incomplete Financial information cannot be used for in-house purchase tests.
• Are you performing an in-house purchase test on the jailbreak device? Jailbreak devices cannot be used for normal purchases. You need to reinstall the device or find a device without jailbreak.
• Whether you can connect to the Apple Server normally. You can visit the IAP section of the Apple Developer Forum. If the Apple Server is down, there should be a heated discussion.

Original article: http://onevcat.com/2013/11/ios-iap-checklist/