iOS Data Storage Guidelines
2014-08-20 09:18
232 查看
https://developer.apple.com/icloud/documentation/data-storage/index.html
iCloud includes Backup, which automatically backs up a user’s iOS device daily over Wi-Fi. Everything in your app’s home directory is backed up, with the exception of the application bundle itself, the caches directory, and temp directory. Purchased music,
apps, books, the Camera Roll, device settings, home screen and app organization, messages, and ringtones are backed up as well. Because backups are done wirelessly and stored in iCloud for each user, it’s best to minimize the amount of data that’s stored for
your app. Large files will lengthen the time it takes to perform a backup and consume more of a user’s available iCloud storage.
To ensure that backups are as efficient as possible, store your app’s data according to the following guidelines:
Only documents and other data that is user-generated, or that cannot otherwise be recreated by your application, should be stored in the <Application_Home>/Documents directory and will
be automatically backed up by iCloud.
Data that can be downloaded again or regenerated should be stored in the<Application_Home>/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.
Data that is used only temporarily should be stored in the <Application_Home>/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.
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.
To learn more about app data and backups, read Make
App Backups More Efficient in the iOS App Programming Guide and technical note: How do I prevent files from being backed up
to iCloud and iTunes?
Overview
iCloud includes Backup, which automatically backs up a user’s iOS device daily over Wi-Fi. Everything in your app’s home directory is backed up, with the exception of the application bundle itself, the caches directory, and temp directory. Purchased music,apps, books, the Camera Roll, device settings, home screen and app organization, messages, and ringtones are backed up as well. Because backups are done wirelessly and stored in iCloud for each user, it’s best to minimize the amount of data that’s stored for
your app. Large files will lengthen the time it takes to perform a backup and consume more of a user’s available iCloud storage.
Storing Your App’s Data Efficiently
To ensure that backups are as efficient as possible, store your app’s data according to the following guidelines:Only documents and other data that is user-generated, or that cannot otherwise be recreated by your application, should be stored in the <Application_Home>/Documents directory and will
be automatically backed up by iCloud.
Data that can be downloaded again or regenerated should be stored in the<Application_Home>/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.
Data that is used only temporarily should be stored in the <Application_Home>/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.
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.
More Information
To learn more about app data and backups, read MakeApp Backups More Efficient in the iOS App Programming Guide and technical note: How do I prevent files from being backed up
to iCloud and iTunes?
相关文章推荐
- 2.23 Apps must follow the iOS Data Storage Guidelines or they will be rejected
- 2.23 Apps must follow the iOS Data Storage Guidelines or they will be rejected
- iOS Data Storage Guidelines 和 "do not back up"文件属性
- 2.23 Apps must follow the iOS Data Storage Guidelines or they will be rejected
- Apps must follow the iOS Data Storage Guidelines or they will be rejected
- 根据苹果最新审核指导意见2.23章节,app应用必须遵守iOS数据储存指导方针(iOS Data Storage Guidelines ),否则应用将被拒。
- iOS Data Storage Guidelines 和 "do not back up"文件属性
- 2.23 Apps must follow the iOS Data Storage Guidelines or they will be rejected
- ios 文件存储 iOS Data Storage Guidelines 和 "do not back up"文件属性
- 2.23 Apps must follow the iOS Data Storage Guidelines or they will be rejected
- iOS Data Storage Guidelines 和 "do not back up"文件属性
- ios 审核 2.23 iOS Data Storage 解决方案
- IOS Data Storage
- iOS-94-解决被拒:5. 1.1 Legal: Privacy - Data Collection and Storage
- IOS上线被拒-Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
- 《iOS Human Interface Guidelines》——Accessing User Data
- 查看由iOS中CoreData框架生成的.sqlite表结构
- iOS开发笔记 7、数据【Preferences、文件、库、Core Data】
- Designing Data Storage Architecture - Understanding Block Blobs and Page Blobs
- Designing Data Storage Architecture-Windows Azure Storage Abstractions and their Scalability Targets