为什么Apple的PackagedDocument MacOS iCloud示例项目找不到URLForUbiquityContainerIdentifier？(Why does Apple's PackagedDocument MacOS iCloud sample project not find URLForUbiquityContainerIdentifier?)

 我一直在尝试使用iCloud示例代码和教程，以便在我们的MacOS和iOS产品之间开发一个同步系统。 在iOS方面，我在构建和运行操作iCloud Documents容器中的数据的代码时没有任何问题，但在MacOS方面，使用Apple MacOS PackagedDocument示例项目，我无法在iCloud中成功放置任何数据。 我认为基本问题是我的应用程序的URLForUbiquityContainerIdentifier无法找到，可能是由于iCloud权利规范中的一些错误。 但是，经过大量时间花在开发人员门户和Xcode 6 / PackagedDocument设置上，我一直无法找到问题的根源。 
 
 我的iCloud帐户以前是MobileMe帐户，用于在MacOS和iOS设备之间同步Apple应用程序，因此我相信我的iCloud帐户可以正常运行。 
 
 在这里，我将说明我指定调用以获取iCloud Documents容器的不同方法。 无论如何指定，获取iCloud容器URL的调用都返回nil： 
 
    // remember our ubiquity container NSURL for later use
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"icloud.com.mycompany.PackagedDocument"];
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"7G3Z4SV5WT.com.mycompany.PackagedDocument"];
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:nil];
 
 在我的iOS实验中，此URLForUbiquityContainerIdentifier调用始终获取所需的URL。 
 
 该应用程序的CFBundleIdentifier是com.mycompany.PackagedDocument 
 
 iCloud授权密钥指定如下： 
 
 com.apple.application-identifier键值为$（TeamIdentifierPrefix）com.mycompany.PackagedDocument 
 
 com.apple.developer.icloud-services键值为CloudDocuments 
 
 com.apple.developer.icloud-container-identifiers键值为iCloud。$（CFBundleIdentifier） 
 
 和com.apple.developer.ubiquity-container-identifiers键值是iCloud。$（CFBundleIdentifier） 
 
 我也试过这个视频教程中的代码，但在尝试获取普遍容器时得到相同的nil结果： 
 
    - (IBAction)saveToIcloud:(id)sender {

    NSFileManager *fm = [NSFileManager defaultManager];

    NSURL *directory = [[fm URLForUbiquityContainerIdentifier:@"7G3Z4SV5WT.com.mycompany.PackagedDocument"]
        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm URLForUbiquityContainerIdentifier:@"iCloud.com.mycompany.PackagedDocument"]
                        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm URLForUbiquityContainerIdentifier:nil]
                        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm 

    if (directory) {
        [fm createDirectoryAtURL:directory withIntermediateDirectories:NO attributes:nil error:NULL];

        NSURL *filepath = [NSURL URLWithString:@"/Users/leg/Desktop/myjpeg.jpg"];

        NSURL *destination = [directory URLByAppendingPathComponent:[filepath lastPathComponent]];

        [fm setUbiquitous:YES itemAtURL:filepath destinationURL:destination error:nil];
    }
}
 
 总之，我认为该问题必须与我的iCloud权利规范和/或访问iCloud Document容器所需的其他规范有关。 如果有人对我可能发生的事情有所了解，我将非常感谢他们的反馈。 如果做不到这一点，也许有人可以指出我在使用非iOS ，macos iCloud Documents示例代码。 
 
 附加信息 
 
 我在控制台日志PackagedDocument启动时看到以下消息： 
 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.ubiquity-container-identifiers 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.icloud-container-identifiers 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.ubiquity-container-identifiers 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.icloud-container-identifiers 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.ubiquity-container-identifiers 
 
 
 9/2/15 5:19:11.966 PM taskgated-helper [14145]：不满意的权利com.apple.developer.icloud-container-identifiers 
 
 
 9/2/15 5:19:11.967 PM taskgated-helper [14145]：由于配置文件，允许pid = 14144的权利 
 
 
 更多信息 
 
 我用一个有效的iOS iCloud示例项目进行了实验，以验证PackagedDocument iCloud容器： 
 
 我将iOS示例的Capabilites / iCloud设置从“使用默认容器”更改为“指定自定义容器”。 我检查了示例的默认容器并检查了“iCloud.com.mycompany.PackagedDocument”。 
 
 然后我更改了URLForUbiquityContainerIdentifier调用： 
 
    from:  NSURL *baseURL = [[NSFileManager defaultManager]URLForUbiquityContainerIdentifier:nil];

    to:    NSURL *baseURL = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"iCloud.com.mycompany.PackagedDocument"];
 
 现在，当我运行这个iOS应用程序时，它会创建PackagedDocument iCloud容器并将其用于其数据 - 这正是我一直在尝试使用PackagedDocument MacOS示例。 
 
 然后我回到MacOS PackagedDocument项目并运行它以查看URLForUbiquityContainerIdentifier调用现在是否会找到容器。 它没有。 即使容器现在肯定存在，Nil仍然返回。 
 
 我想这意味着它仍然是某种权利问题。 
 
 更多信息 
 
 
 
 我进行了另一个实验，我从我的常用开发人员系统（Yosemite 10.10.5）的Xcode 6.4 / Preferences / Actions / Export Accounts ...导出我的开发者身份，然后在Mavericks 10.9.5下重新启动我的MacBook Pro并使用Xcode导入身份6.1 /偏好/行动/进口帐户...... （在我将其升级到Yosemite之前，Mavericks系统磁盘实际上是我的MacBook Pro系统磁盘的Carbon Copy。）现在，当我在Mavericks中构建并运行PackagedDocument时， 一切都运行良好 。 
 
 
 然后我重新启动回Yosemite并删除我的身份并使用Xcode 6.1 / Preferences / Actions / Import Accounts ...导入身份。 现在，当我在Yosemite中构建并运行PackagedDocument时，它仍然不起作用 - 找不到iCloud容器 。 
 
 
 然后我决定在干净安装的El Capitan（10.11 Beta 5）/ Xcode 6.4中尝试相同的实验。 同样，它仍然无法工作 - 找不到iCloud容器 。 
 
 
 最后，我决定再尝试一次。 我决定尝试打开iCloud Drive 。 但是，因为我不想将我工作的iCloud帐户转换为iCloud Drive ，所以我决定为测试创建一个新的iCloud ID，并打开iCloud Drive 。 现在，当我使用iCloud Drive在El Capitan中构建和运行PackagedDocument时， 一切都运行良好 。 
 

I have been experimenting with iCloud sample code and tutorials in order to develop a syncing system between our MacOS and iOS products. On the iOS side I have had no problem building and running code that manipulates data in an iCloud Documents container, but on the MacOS side, using the Apple MacOS PackagedDocument sample project, I have not been able to successfully place any data in my iCloud. I believe the basic problem is that the URLForUbiquityContainerIdentifier for my app can not be found, probably due to some error in iCloud entitlements specification. But, after much time spent fiddling with the developer portal and Xcode 6/PackagedDocument settings, I have been unable to locate the source of the problem.
 
My iCloud account was previously a MobileMe account and is used to synchronize the Apple apps between MacOS and iOS devices, so I believe my iCloud account is working without problems.
 
Here I am illustrating the different ways that I have specified the call to get the iCloud Documents container. The call to get the iCloud container URL returns nil regardless of how it is specified:
 
    // remember our ubiquity container NSURL for later use
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"icloud.com.mycompany.PackagedDocument"];
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"7G3Z4SV5WT.com.mycompany.PackagedDocument"];
    _ubiquityContainer = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:nil];
 
In my iOS experiments, this URLForUbiquityContainerIdentifier call always gets the desired URL.
 
The CFBundleIdentifier for the app is com.mycompany.PackagedDocument
 
The iCloud entitlement keys are specified as follows:
 
The com.apple.application-identifier key value is $(TeamIdentifierPrefix)com.mycompany.PackagedDocument
 
The com.apple.developer.icloud-services key value is CloudDocuments
 
The com.apple.developer.icloud-container-identifiers key value is iCloud.$(CFBundleIdentifier)
 
and the com.apple.developer.ubiquity-container-identifiers key value is iCloud.$(CFBundleIdentifier)
 
I also tried code from this video tutorial, but get the same nil result when trying to get the ubiquity container:
 
    - (IBAction)saveToIcloud:(id)sender {

    NSFileManager *fm = [NSFileManager defaultManager];

    NSURL *directory = [[fm URLForUbiquityContainerIdentifier:@"7G3Z4SV5WT.com.mycompany.PackagedDocument"]
        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm URLForUbiquityContainerIdentifier:@"iCloud.com.mycompany.PackagedDocument"]
                        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm URLForUbiquityContainerIdentifier:nil]
                        URLByAppendingPathComponent:@"Documents"];
    directory = [[fm 

    if (directory) {
        [fm createDirectoryAtURL:directory withIntermediateDirectories:NO attributes:nil error:NULL];

        NSURL *filepath = [NSURL URLWithString:@"/Users/leg/Desktop/myjpeg.jpg"];

        NSURL *destination = [directory URLByAppendingPathComponent:[filepath lastPathComponent]];

        [fm setUbiquitous:YES itemAtURL:filepath destinationURL:destination error:nil];
    }
}
 
In summary, I believe the problem must have something to do with my specification of iCloud entitlements and/or other specifications necessary to access iCloud Document containers. If anyone has a clue about what may be happening to me, I'd greatly appreciate their feedback. Failing that, maybe someone could point me at working non-iOS, macos iCloud Documents sample code.
 
Additional Information
 
I am seeing the following messages in he console log PackagedDocument start-up:
 
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.ubiquity-container-identifiers
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.icloud-container-identifiers
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.ubiquity-container-identifiers
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.icloud-container-identifiers
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.ubiquity-container-identifiers
 
 
9/2/15 5:19:11.966 PM taskgated-helper[14145]: unsatisfied entitlement com.apple.developer.icloud-container-identifiers
 
 
9/2/15 5:19:11.967 PM taskgated-helper[14145]: allowing entitlement(s) for pid=14144 due to provisioning profile
 
 
More Information
 
I performed an experiment with a working iOS iCloud example project to validate the PackagedDocument iCloud container:
 
I altered the iOS example’s Capabilites/iCloud settings from “Use default container” to “Specify custom containers”. I checked off the example’s default container and checked on “iCloud.com.mycompany.PackagedDocument”.
 
I then changed the URLForUbiquityContainerIdentifier call:
 
    from:  NSURL *baseURL = [[NSFileManager defaultManager]URLForUbiquityContainerIdentifier:nil];

    to:    NSURL *baseURL = [[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:@"iCloud.com.mycompany.PackagedDocument"];
 
Now, when I run this iOS app, it creates the PackagedDocument iCloud container and uses it for its data—-exactly what I’ve been trying to do with the PackagedDocument MacOS sample.
 
I then went back to the MacOS PackagedDocument project and ran it to see if the URLForUbiquityContainerIdentifier call would now find the container. It did not. Nil is still returned even though the container definitely now exists.
 
I suppose that this means it is still an entitlements problem of some kind.
 
Even More Information
 
 
 
I performed another experiment whereby I exported my developer identities from Xcode 6.4/Preferences/Actions/Export Accounts… of my usual developer system (Yosemite 10.10.5,) and then rebooted my MacBook Pro under Mavericks 10.9.5 and imported the identities with Xcode 6.1/Preferences/Actions/ Import Accounts…. (The Mavericks system disk is actually a Carbon Copy of my MacBook Pro system disk before I upgraded it to Yosemite.) Now, when I build and run PackagedDocument in Mavericks, everything works perfectly.
 
 
I then rebooted back into Yosemite and removed my identities and imported the identities with Xcode 6.1/Preferences/Actions/ Import Accounts…. Now, when I build and run PackagedDocument in Yosemite, it still does not work--does not find the iCloud container.
 
 
I then decided to try the same experiment in a clean install of El Capitan (10.11 Beta 5)/Xcode 6.4. Again, it still does not work--does not find the iCloud container.
 
 
And finally, I decided to try one more experiment. I decided to try turning on iCloud Drive. But, because I did not want to convert my working iCloud account to iCloud Drive, I decided to create a new iCloud ID for the test, and to turn on iCloud Drive. Now, when I build and run PackagedDocument in El Capitan with iCloud Drive, everything works perfectly.
 

原文：https://stackoverflow.com/questions/32342813