• 2.23 - Apps must follow the iOS Data Storage Guidelines or they will be rejected
• 11.2 - Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be rejected
In addition, on launch and content download, your app stores 3MB data, which does not comply with the iOS Data Storage Guidelines.
Please verify that only the content that the user creates using your app, e.g., documents, new files, edits, etc. is backed up by iCloud as required by the iOS Data Storage Guidelines. Also, check that any temporary files used by your app are only stored in the/tmp directory; please remember to remove or delete the files stored in this location when it is determined they are no longer needed.
Data that can be recreated but must persist for proper functioning of your app - or because users expect it to be available for offline use - should be marked with the "do not back up" attribute. For NSURL objects, add the NSURLIsExcludedFromBackupKey attribute to prevent the corresponding file from being backed up. For CFURLRef objects, use the corresponding kCRUFLIsExcludedFromBackupKey attribute.
To check how much data your app is storing:
- Install and launch your app
- Go to Settings > iCloud > Storage > Manage Storage
- Select your device
- If necessary, tap "Show all apps"
- Check your app's storage
For additional information on preventing files from being backed up to iCloud and iTunes, see Technical Q&A 1719: How do I prevent files from being backed up to iCloud and iTunes.
If you have difficulty reproducing a reported issue, please try testing the workflow described in Technical Q&A QA1764: How to reproduce bugs reported against App Store submissions.
If you have code-level questions after utilizing the above resources, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
We noticed that your app enables the purchase of content, services, or functionality in the app by means other than the In-App Purchase API, which is not allowed on the App Store.
While the payment system that you have included may conduct the transaction outside of the app, if the purchasable content, functionality, or services are intended to be used in the app, they must be purchased through IAP, within the app - unless it is of the type referenced in Guideline 11.14.
It may be appropriate to revise your app to use the In App Purchase API to provide content purchasing functionality.
In App Purchase provides several benefits, including:
- The flexibility to support a variety of business models.
- Impacting your app ranking by consolidating your sales to one app rather than distributing them across multiple apps.
- The ability to offer additional content to your user. In this way, your app enabled with In App Purchase becomes an effective marketing vehicle to drive additional sales of new content.
For information on In App Purchase, please refer to the following documentation:
Getting Started with In App Purchase on iPhone OS
In-App Purchase Programming Guide
For step-by-step instructions on In App Purchase creation within iTunes Connect, refer to the In-App Purchase Configuration Guide for iTunes Connect