iCloud和正确的配置文件使用情况 [英] iCloud and correct provisioning profile usage

查看:164
本文介绍了iCloud和正确的配置文件使用情况的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有人可以解决这个问题吗?我已经在论坛上发布了我到目前为止一直使用的三个页面.

iCloud和正确的配置文件使用情况 2011年10月30日,上午9:49 我已经为我的AppID启用了iCloud.然后,我创建了3个证书,列为:

  • Mac App
  • Mac Installer
  • 发展

在开发人员证书实用程序中.

我在证书链中下载并安装了证书:

  • 第三方Mac开发人员应用程序(Mac App)
  • 第三方Mac开发人员安装程序(Mac Installer)
  • Mac开发人员(开发)

然后,我创建了2个配置文件:

  • 发展 我选择了应用程序ID,先前创建的开发证书和系统.

  • 生产 我只能选择应用程序ID和Mac应用程序分发签名证书.

我已将开发配置文件成功安装在Profiles Pref Pane中.如果我试图在个人档案"首选项窗格中安装生产个人档案,则会出现未知错误"对话框.这样对吗?无法安装此配置文件?

我将两个配置文件都添加到了Xcode Organizer,并从开发配置文件中选择了"Mac Developer"进行调试,并从生产配置文件中选择了"3rd Party Mac Developer Application"作为发行版.

现在,我可以在Xcode中启动该应用程序,并且它可以按预期运行(启用了iCloud).如果我要归档发行版本并在Finder中启动应用程序,我将得到:

taskgated:已被杀死...因为不允许使用com.apple.developer.ubiquity-container-identifiers权利

是否应该仅将生产资料用于提交给MAS?我有什么问题吗?

steveflack 帖子:6(0) 回复报价添加负面分数添加正面分数 1.回复:iCloud和正确的配置文件使用情况 回应pws在2011年11月4日上午4:23 如果您在Xcode Organizer中查看Production Profile,它说您无法将其安装在设备上-我想这就是为什么它不会安装在Settings应用程序的Profiles窗格中的原因.我只在今天早上才知道这一点-该错误消息并非完全有帮助.

也许我错了,但是这看起来非常可怕,就像您当前无法在MAS之外发布iCloud应用程序一样.看来我们必须将开发人员配置文件与iOS addhoc配置文件一样对待进行测试.

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 2. Re:iCloud和正确的配置文件使用情况 回应steveflack在2011年12月9日下午4:42 你们中的任何人都可以使用生产资料对其进行签名吗?

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 3.回复:iCloud和正确的配置文件使用情况 为了回应steveflack在2011年12月9日下午5:49 有人知道启用了iCloud的生产配置文件时,mac应用程序是否应该在我的开发计算机上运行吗?还是需要将其提交到Mac App Store? 当我使用生产配置文件进行构建和签名时,没有出现任何错误,但是在启动时我得到了该应用程序被杀,因为我没有使用com.apple.developer.ubiquity-container-identifiers的权限".

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 4. Re:iCloud和正确的配置文件使用情况 为了回应Jose Ines Cantu Arrambide在2011年12月17日下午12:08 我也收到此错误.请帮帮我!

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 5. Re:iCloud和正确的配置文件使用情况 为了回应Allen Dunahoo在2011年12月17日下午12:23 我要求苹果公司提供技术支持,我会让您知道他们说什么. 但是我的猜测是,要进行Beta测试,您应该在mac设置部分中添加每个mac系统,并告诉每个Beta用户通过双击将设置配置文件添加到他们的系统中.

我敢打赌,只有通过将应用程序发送到Mac App Store,生产配置文件才能工作.

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 6. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午12:46回应Jose Ines Cantu Arrambide 如果我无法运行该应用程序,则无法将其上传到Apple.

很奇怪,但是我现在不能编译任何其他Mac应用程序,iCloud或没有iCloud.我曾经在另一台计算机上尝试过,但无法正常工作!

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 7.回复:iCloud和正确的配置文件使用情况 在2011年12月17日下午1点04分回应Allen Dunahoo 哇,您无法编译或无法运行该应用程序?您可以在不签名的情况下进行编译吗?

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 8.回复:iCloud和正确的配置文件使用情况 在2011年12月17日下午1月29日回应Jose Ines Cantu Arrambide 好吧,我猜我可以编译它,但是我收到此错误(每个应用程序都会略有变化):

错误:无法启动'/Users/padsoftware/Library/Developer/Xcode/DerivedData/Scrawl-heofvoywsunchdhjowxkvkoiqvan/Build/Products/Release/Scrawl.app/Contents/MacOS/Scrawl'

很奇怪:我没有此应用程序的沙箱,iCloud或权利.在那些我做我得到同样的错误.我已经重新安装了Xcode 4.2.1和OS X Lion 10.7.2.

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 9.回复:iCloud和正确的配置文件使用情况 在2011年12月17日下午1:31回应Allen Dunahoo 没有代码签名,我会得到同样的错误.这真让我讨厌.与Apple联络无济于事,因为它们会减慢速度

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 10. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午2点10分回应Allen Dunahoo 当我没有将mac uuid添加到mac设置门户时,我也遇到了这种情况,您的设置配置文件是否安装在Lion的系统首选项中? 但是由于它在您不进行代码签名时会崩溃,因此没关系

Jose Ines Cantu Arrambide 帖子:166(1) 回复报价添加负面分数添加正面分数 11. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午2点12分回应Allen Dunahoo 如果您从实用程序中打开Console.app,启动时是否还会得到其他信息?

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 12. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午2点15分回应Jose Ines Cantu Arrambide 可悲的是,不,我得到的信息相同.

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 13. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午2点19分回应Allen Dunahoo 顺便说一句,我刚刚将其发布在stackoverflow中. Xcode错误:无法启动

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价 14. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午2:48回应Allen Dunahoo 问题是我缺少与开发证书相关联的私钥+公钥...我也出于某种原因无法将我正在使用的那些公钥导入到钥匙串中. 我生成了CSR(用于构建公钥/私钥并将其添加到钥匙串中),并创建了新的证书/设置配置文件,并更新了构建设置以指向新内容. 有人说这为他们解决了.我会尝试的,让您知道它是否有效.

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价编辑 15. Re:iCloud和正确的配置文件使用情况 在2011年12月17日下午4:28回应Allen Dunahoo 好的,结果如下: 开发配置文件的代码符号:成功. 生产资料代码符号:失败.控制台中的错误:任务分配时间为12/17/11 4:22:50.184 PM:已杀死com.allendunahoo.Scrawl [pid 5772],因为不允许使用com.apple.developer.ubiquity-container-identifiers权限"/p>

我不明白:开发概要文件的标题中包括:8W27B5T8XC.但是,生产资料"没有该内容.我怀疑这是问题的一部分.现在,有人对解决这个庞大而丑陋的问题有任何想法吗?

P.S.我需要com.apple.developer.ubiquity-container-identifiers,因为此应用程序使用iCloud.

消息是由AllenDunahoo于2011年12月17日下午4:28编辑的

艾伦·杜纳霍(Allen Dunahoo) 戈申 帖子:700(6) 回复报价编辑 16. Re:iCloud和正确的配置文件使用情况 为了回应Allen Dunahoo在2011年12月17日下午4:30 这是我的权利:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
<plist version="1.0">
<string>8W27B5T8XC.com.allendunahoo.Scrawl</string>
</plist>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
<plist version="1.0">
<array>
<string>$(TeamIdentifierPrefix)8W27B5T8XC.com.allendunahoo.Scrawl</string>
</array>
</plist>

解决方案

您似乎已经了解了其中的大部分内容:

  • iCloud支持仅适用于从App Store运送的应用程序.
  • 您不能使用生产配置文件在开发计算机上运行可执行文件.仅可通过Mac App Store使用.
  • 您的发布目标可能会使用第三方Mac开发人员应用程序(Mac App)"证书进行签名.这是构建发送到应用程序商店的存档所必需的,但是您不能在本地运行该应用程序.相反,您应该将签名切换到用于运行本地发行版的"Developer"证书,然后切换回"3rd Party Mac Developer Application(Mac App)"进行存档以供发行.

Could anyone please solve this? I've posted the forum three I've been using so far.

iCloud and correct provisioning profile usage Oct 30, 2011 9:49 AM I've enabled iCloud for my AppID. Then, I've created 3 certificates, listed as:

  • Mac App
  • Mac Installer
  • Development

in the Developer Certificate Utility.

I downloaded and installed the certificates in my keychain:

  • 3rd Party Mac Developer Application (Mac App)
  • 3rd Party Mac Developer Installer (Mac Installer)
  • Mac Developer (Development)

Then, I've created 2 provisioning profiles:

  • Development I selected the App ID, the previously created development certificate and the Systems.

  • Production I can only select the App ID and the Mac Application Distribution Signing Certificate.

I installed the development profile in the Profiles Pref Pane successfully. If I am trying to install the production profile in the Profiles Pref Pane, I am getting an "Unknown Error" dialog. Is this correct? This profile can't be installed?

I added both profiles to the Xcode Organizer and selected "Mac Developer" from the development profile for debugging and "3rd Party Mac Developer Application" from the production profile for the release version.

Now, I can launch the app in Xcode and it works as expected (with iCloud enabled). If I am archiving the release version and launch the app in the Finder, I am getting:

taskgated: killed ... because its use of the com.apple.developer.ubiquity-container-identifiers entitlement is not allowed

Is the production profile supposed to be used only for submitting to the MAS? Did I something wrong?

steveflack Posts : 6 (0) ReplyQuoteAdd Negative ScoreAdd Positive Score 1. Re: iCloud and correct provisioning profile usage In response to pws on Nov 4, 2011 4:23 AM If you look at the Production Profile in the Xcode Organizer it says you can't install it on devices - which I guess is why it won't install in the Profiles Pane in the Settings app. I only figured this out this morning - that error message isn't exactly helpful.

Maybe I'm wrong but it's looking horribly like you currently can't ship iCloud apps outside of MAS. It looks like we'll have to treat the dev profile like the iOS adhoc profiles for testing.

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 2. Re: iCloud and correct provisioning profile usage In response to steveflack on Dec 9, 2011 4:42 PM Were any of you able to sign it with production profiles?

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 3. Re: iCloud and correct provisioning profile usage In response to steveflack on Dec 9, 2011 5:49 PM Does anyone know if a mac app should run on my development machine when using a Production Profile with iCloud enabled? Or does it need to be submitted to the Mac App Store ? When I build and sign with the production profile I get no errors, but I get the "app was killed because I did not have permission to use the com.apple.developer.ubiquity-container-identifiers" when launching.

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 4. Re: iCloud and correct provisioning profile usage In response to Jose Ines Cantu Arrambide on Dec 17, 2011 12:08 PM I'm getting this error as well. Please help me!

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 5. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 12:23 PM I requested technical support from Apple, I'll let you know what they say. But my guess is that to do Beta Testing, you should add each mac system in your mac provisioning section and tell each beta user to add the provisionging profile to their system by double clicking.

I'm betting that the production profile only works by sending the app to the Mac App Store.

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 6. Re: iCloud and correct provisioning profile usage In response to Jose Ines Cantu Arrambide on Dec 17, 2011 12:46 PM If I can't run the app, there is no way I will upload it to Apple.

Strange, but I can't compile any other Mac app right now, iCloud or no iCloud. I've evern tried on a diffrent computer, and it doesn't work!

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 7. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 1:04 PM Wow, you can't compile or cant run the app? Can you compile without signing?

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 8. Re: iCloud and correct provisioning profile usage In response to Jose Ines Cantu Arrambide on Dec 17, 2011 1:29 PM Well I guess I can compile it, but I get this error (it changes slightly with each app):

error: failed to launch '/Users/padsoftware/Library/Developer/Xcode/DerivedData/Scrawl-heofvoywsunchdhjowxkvkoiqvan/Build/Products/Release/Scrawl.app/Contents/MacOS/Scrawl'

It's odd: I don't have sandboxing, iCloud, or entitlements for this app. On the ones I do i get the same error. I have already reinstalled Xcode 4.2.1 and OS X Lion 10.7.2.

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 9. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 1:31 PM Without code signing I get the same error. This is really annoying me. Contacting Apple won't help, because they are way to slow

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 10. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 2:10 PM This also happened to me when I did not added the mac uuids to the mac provisioning portal, does your provisioning profile installs in your system preferences on Lion? But since it blows when you are not code signing it, it should not matter

Jose Ines Cantu Arrambide Posts : 166 (1) ReplyQuoteAdd Negative ScoreAdd Positive Score 11. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 2:12 PM If you open Console.app from utilities do you get any extra info when launching?

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 12. Re: iCloud and correct provisioning profile usage In response to Jose Ines Cantu Arrambide on Dec 17, 2011 2:15 PM Sadly, no, I get the same info.

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 13. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 2:19 PM Btw, I just posted this in stackoverflow. Xcode error: failed to launch

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuote 14. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 2:48 PM The problem was I was missing the private+public keys associated with the development certificate... I also, couldn't import the ones I was using into keychain for some reason. I generated the CSR (which builds public/private keys and adds them to keychain) and created a new certificate/provisioning profile and updating my build settings to point to new stuff. Somebody said this fixed it for them. I'll try it and let you know if it works.

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuoteEdit 15. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 4:28 PM OK, here are the results: Development Profile code sign: success. Production Profile code sign: failed. Error in console:"12/17/11 4:22:50.184 PM taskgated: killed com.allendunahoo.Scrawl[pid 5772] because its use of the com.apple.developer.ubiquity-container-identifiers entitlement is not allowed"

I don't get it: the Development Profile has this included in the title: 8W27B5T8XC. However, the Production Profile does not have that. I suspect that is part of the problem. Now, does anyone have any ideas on hw to fix this huge and ugly problem?

P.S. I need the com.apple.developer.ubiquity-container-identifiers becuase this app uses iCloud.

Message was edited by AllenDunahoo on 12/17/11 at 4:28 PM

Allen Dunahoo Goshen , CT Posts : 700 (6) ReplyQuoteEdit 16. Re: iCloud and correct provisioning profile usage In response to Allen Dunahoo on Dec 17, 2011 4:30 PM This is my entitlements:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
<plist version="1.0">
<string>8W27B5T8XC.com.allendunahoo.Scrawl</string>
</plist>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
<plist version="1.0">
<array>
<string>$(TeamIdentifierPrefix)8W27B5T8XC.com.allendunahoo.Scrawl</string>
</array>
</plist>

解决方案

You seem like you figured out most of it:

  • iCloud support is only available for applications shipping from the App store.
  • You cannot use the Production provisioning profile to run executables on your development machine. This is only for use via the Mac App Store.
  • Your Release target probably signs with your "3rd Party Mac Developer Application (Mac App)" certificate. This is required for building the Archive you send to the app store, but you cannot run the application locally. Instead, you should switch the signature to your "Developer" certificate for running a local release build, and switch back to "3rd Party Mac Developer Application (Mac App)" to archive for release.

这篇关于iCloud和正确的配置文件使用情况的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆