iCloud Storage

• NEW: If you call either stringByResolvingSymlinksInPath or stringByStandardizingPath on a path descended from your container, you'll never be able to use the result to successfully perform a coordinated read.
• NEW: On KVS, the per-key limit has been raised to 64Kb (to match the per-app limit); and the maximum number of keys has been raised to 256.
• 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.
• Provisioning Profiles no longer need to be enabled for iCloud in the iOS Provisioning Portal. All newly generated provisioning profiles are now automatically enabled for iCloud. If you are using an Xcode managed Team Provisioning Profile, click refresh in the Xcode Organizer to obtain a new iCloud-enabled profile. To enable all other provisioning profiles for iCloud, simply regenerate your profiles in the iOS Provisioning Portal.
• If your application is using the NSMetadataQuery class, you must set a predicate, even though the predicate itself is ignored.
• In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
• FIXED: To use iCloud prior to beta 5, you had 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.Starting in beta 5, to enable iCloud storage within your apps, simply click the “Enable Entitlements” checkbox in the Summary pane of your project. Xcode will create a custom entitlements file for your project that automatically includes your Team ID. You can add additional iCloud Container values as required by your application. (Note that you must regenerate your existing provisioning profiles, either with Xcode or in the iOS Provisioning Portal, to use iCloud storage.)If you specify a custom identifier string for your iCloud Key-Value Store or iCloud Container entitlement values, you no longer need to prepend your Team ID to the beginning of the string. Xcode will prepend your Team ID to these entries automatically
• The container identifier string you pass to the URLForUbiquityContainerIdentifier: method of NSFileManager MUST include the team ID at the beginning of the string. As a convenience, if you pass nil, Foundation uses the first document container ID specified in your app's entitlements.
• There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
• FIXED: In this beta, document-based applications cannot always detect when files change, move, or are deleted out from underneath them.
• 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.

• File names are case-insensitive in OS X but case-sensitive in iOS. This can lead to problems when syncing files between the two. You should take steps on iOS to avoid creating files whose names differ only by case.