My application is rejected in order not to set the “do not back up” attribute for the two internal files that I use (and save in / Documents). I set the attribute and it no longer supports these files (~ 11.5 MB).
However, it still supports 28kb of some data. I deleted all the data from the / Documents folder and put it in / tmp to make sure that nothing in the documents could be copied. I confirmed / Documents are empty for my application after this change, and yet iCloud manages to find 28kb of data for backup.
How can I pinpoint that this data is intended to prevent backups? I don’t want to be rejected again, so I want to check that the application takes up 0kb of backup storage in iCloud.
2.23
We found that your application does not support the iOS Data Warehouse Recommendations that are required in the App Store Review Guide.
In particular, we found that at startup your application stores 11.53 MB. to check how much data is stored in your application:
- Install and run the application
- Go to Settings> iCloud> Storage and Backup> Storage Management
- If necessary, tap "Show all applications"
- Check application store
IOS storage guides indicate that only content the user creates your application, such as documents, new files, changes, etc. can be saved in the / Documents directory - and backed by iCloud.
Temporary files used by your application should only be stored in the / tmp directory; do not forget to delete files stored in this place when the user exits the application.
Data that can be recreated, but must be saved for your application to function properly — or because customers 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 kCFURLIsExcludedFromBackupKey attribute.
For more information, see Technical Q & A 1719: How to prevent files from being backed up in iCloud and iTunes ?.
You must review your application to meet the requirements of the iOS Storage Guidelines. For discrete code-level questions, you can consult with Apple Developer Technical Support. Be sure to prepare any symbolic crash logs, screenshots, or steps to reproduce problems when the DTS engineer comes along. For information on how to symbolize and read the fault log, see Technical Note TN2151 Understanding and Analyzing iPhone OS Fault Report.