iOS Data Storage Guidelines.

Leave a comment

Unfortunately i received this from Apple today. Before submitting your app, make sure check this out first.

We found that your app does not follow the iOS Data Storage Guidelines, which is not in compliance with the App Store Review Guidelines.

In particular, we found that the app content is not being stored appropriately.

The iOS Data Storage Guidelines specify:

“1. Only documents and other data that is user-generated, or that cannot otherwise be recreated by your application, should be stored in the /Documents directory and will be automatically backed up by iCloud.

2. Data that can be downloaded again or regenerated should be stored in the /Library/Caches directory. Examples of files you should put in the Caches directory include database cache files and downloadable content, such as that used by magazine, newspaper, and map applications.

3. Data that is used only temporarily should be stored in the /tmp directory. Although these files are not backed up to iCloud, remember to delete those files when you are done with them so that they do not continue to consume space on the user’s device.

4. Use the “do not back up” attribute for specifying files that should remain on device, even in low storage situations. Use this attribute with data that can be recreated but needs to persist even in low storage situations for proper functioning of your app or because customers expect it to be available during offline use. This attribute works on marked files regardless of what directory they are in, including the Documents directory. These files will not be purged and will not be included in the user’s iCloud or iTunes backup. Because these files do use on-device storage space, your app is responsible for monitoring and purging these files periodically.”

For example, only content that the user creates using your app, e.g., documents, new files, edits, etc., may be stored in the/Documents directory – and backed up by iCloud. 

Temporary files used by your app should only be stored in the /tmp directory; please remember to delete the files stored in this location when the user exits the app.

Data that can be recreated but must persist for proper functioning of your app – or because customers expect it to be available for offline use – should be marked with the “do not back up” attribute. For more information, please see Technical Q&A 1719: How do I prevent files from being backed up to iCloud and iTunes?.

It would be appropriate to revise your app to meet the requirements of the iOS Data Storage Guidelines. 

For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to prepare any symbolicated crash logs, screenshots, or steps to reproduce the issues for when the DTS engineer follows up. For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports.

Advertisements

[Tip] Target failed to run: Remote exception encountered: ‘Failed to get task for pid #’

3 Comments

I got this error just recently when i tried to use the instrument to profile my iPad application on the device. And when i selected “Profile” from the menu, and instrument was opened. Then i selected “Allocations” or “Leaks”, i just heard “Funk” and then nothing happened. So i checked out the Console and found out some errors about missing plug-ins for these selected functions. So bascially, it’s because some plug-in in your Xcode application folder was missing or crrupt. So better remove Xcode completely through Command line “sudo /Developer/Library/uninstall-devtools --mode=all“,then reinstall it. You should be good to go.  

Then when i rerun my app with instrument i received another error which was the topic of this post. After searching a little bit. It’s actually very easy to fix.

1.Make sure, the “Profile” scheme is using “debug” not “release” build configuration

Here is the way how to change it: In Xcode4, select “Product/Edit Scheme” from the top menu then click on the “Profile” button on the left panel. Under the “Info” tab you will see “Build configuration”, make sure “Debug” is selected.

Profile

2.This error would pop out also if you test your app with a “distribution profile” selected for your app, so make sure choose “Development” provisioning file in code-sign settings.

Then enjoy testing with your instrument.

Shooting video with upcoming American rap star Mann for our app promotion

Leave a comment


Taken at Annenberg School for Communication & Journalism (ASC)

Error: “No Packager exists for the type of archive” on Xcode4 with iOS 4.3 and later

Leave a comment

When you archive the project and try to share with ipa. You probably would see this error. That’s not hard to fix. I found the solution here.

http://stackoverflow.com/questions/5271496/xcode4-ios-4-3-no-packager-exists-…

Basically, you need to set the flag “Skip Install” in the “Build Settings” for every dependency project to “YES“. But leave the main project to “NO”. Then do a clean and rebuild. You should see “iOS App Store Package(.ipa)” then.

Walking in the community~~

Leave a comment

Pentagon

Leave a comment

Untitled

Leave a comment

Older Entries