iCloud Backup

• As this is beta software, it is recommended that you do not use the iCloud services to store any critical data or information. If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We suggest you also manually back up your device with iTunes.
• In the iOS 5 beta, support for data protection in iCloud Backup is unavailable. Apps that have protected files will not have any of their data or metadata backed up as a result.
• After restoring, you may not be able to back up again because the device still thinks it's restoring. To workaround this issue try syncing apps or media that are missing form iTunes or try deleting your iCloud account and adding it back.
• If you delete your backup, the feature will be disabled but settings may still indicate that it is enabled and you will have to toggle the BackUp to Cloud switch in Settings.
• For compatibility reasons, this version of the iOS 5 beta requires that all files be backed up again, instead of only those files that have changed since your last backup. This may cause a warning that your account is over quota. In case the warning occurs, you can delete your oldest backup to free up space and then initiate a backup.

iCloud Storage

• During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
• If your application is using the NSMetadataQuery class, you must set a predicate, even though the predicate itself is ignored.
• The Foundation framework doesn't include the team ID when looking for an app's mobile documents container. The Team ID must be included at the beginning of the identifier string passed to theURLForUbiquityContainerIdentifier: method.
• In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
• In this beta, if you want to use iCloud, you have to manually specify various container identifiers (your application's Display set) within an Entitlements file for both of your Mac OS X and iOS projects.
• There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
• In this beta, document-based applications cannot always detect when files change, move, or are deleted out from underneath them.
• NEW: In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that they're supposed to receive, especially:
  • presentedItemDidChange
  • presentedSubitemDidAppearAtURL:
  • presentedSubitemDidChangeAtURL:

  You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires. You can also use FSEvents to observe file system changes

• In this beta, messages about changes to files in a directory are not getting delivered to objects that adopt the NSFilePresenter protocol.
• While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device.The debug profile can be obtained from http://connect.apple.com. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
  1. Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
  2. Reproduce the bug.
  3. Sync with iTunes to pull the logs off your device.
  4. Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.

  These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.