Application rejected due to non-compliance with iOS storage rules

Question

We store data in the application’s document directory, and we received a rejection from the application. We tried to use the “do not back up” attribute to store data in the current version using the code below.

- (BOOL)addSkipBackupAttributeToItemAtURL:(NSURL *)URL{ const char* filePath = [[URL path] fileSystemRepresentation]; const char* attrName = "com.apple.MobileBackup"; u_int8_t attrValue = 1; int result = setxattr(filePath, attrName, &attrValue, sizeof(attrValue), 0, 0); return result == 0; } 

We used it in accordance with the iOS Storage Guide.

In an earlier version, we also tried to save the data in a private folder. But we could not get approval of the application.

Could you give us a more detailed description of why we cannot get approval of the application? or do we still need any other code changes regarding data storage? So, we can get approval, and we have a new version of the application in iTunes.

Answer 1

I think the @Jasarien comment is the correct answer, but there was no command, and this question is relatively new, so I will expand.

For others, to see the deviation you get:

The iOS Storage Guide states:

• Only documents and other data created by the user or that cannot be re-created by your application should be stored in the / Documents directory and will be automatically supported by iCloud.

• Data that can be reloaded or regenerated must be stored in the / Library / Caches directory. Examples of files you need to put in the Caches directory include database cache files and downloadable content, such as those used by magazines, newspapers, and map apps.

• Data that is only used temporarily should be stored in the / tmp directory. Although these files are not supported by iCloud, be sure to delete these files when you are finished with them so that they do not continue to use the space on the user's device.

• Use the Do Not Back Up Attribute attribute to specify files that should remain on the device, even in low-storage situations. Use this attribute with data that can be recreated, but it must be preserved even in low-storage situations for your application to work properly or because clients expect it to be available offline. This attribute works with marked files no matter what directory they are in, including the Documents directory. These files will not be cleaned up and will not be included in the iCloud or iTunes user backup. Since these files use storage space on the device, your application is periodically responsible for monitoring and cleaning these files.

For example, only content created by the user using your application, such as documents, new files, changes, etc., can be stored in the / Documents directory and supported 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 work properly, or because clients expect it to be available for offline use, should be marked with the “do not back up” attribute. For more information, see Technical Q & A 1719: How to prevent backing up files in iCloud and iTunes ?.

So, I understand why you would use "not backup" and expect to be consistent, but I think as @Jasarien said. They mean that you go to more discrete directories, such as cache or pace.

In fact, what is sure to go through the review is switching to Core Data and using internal SQLite - but that probably works too much.

So, to wrap - a message on how to save caches or tmp - Where to save files in iOS 5 applications? (actually, maybe it was a duplicate of this ...: - /)

GL! Oded

- Change -

Another good post: https://stackoverflow.com/questions/8164868/ios-data-storage-guidelines-available-since-when

- Edit # 2 -

And another good post: iOS 5 does not allow you to store downloaded data in the Documents directory?

I guess I should just point out duplicates ... :)

Answer 2

Take a look at this link http://developer.apple.com/library/ios/#qa/qa1719/_index.html#//apple_ref/doc/uid/DTS40011342 The code you use is compatible with 5.0.1, not 5.1 and later. You must use Cache for <= 5.0. But the best solution would be to deploy for 5.1 and later instead of 5.0, because if you have a lot of data, most likely the cache will be cleared earlier. Hope this helps.