ios Xcode Watchkit:没有任何有效的配置文件允许指定的权利:beta-reports-active, com.apple.security.application-groups
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/29729437/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Xcode Watchkit: None of the valid provisioning profiles allowed the specified entitlements: beta-reports-active, com.apple.security.application-groups
提问by Nerdy Lime Apps
Yes, I know that there are a lot of these questions floating around and I know that the answer to all of them was:
是的,我知道有很多这样的问题,我知道所有这些问题的答案都是:
Log into Developer Member Center
登录开发者会员中心
Go to Identifiers, profiles, etc
转到标识符、配置文件等
Click Edit and then Generate on your provisioning profile
单击编辑,然后在您的配置文件上生成
That didn't work for me! I developed my application in Xcode 6.4 Beta 1 and with WatchKit. I tried submitting it but after seeing that error, I figured maybe I should try submitting it with a nonbeta version of Xcode. By the way here is that error:
那对我不起作用!我在 Xcode 6.4 Beta 1 和 WatchKit 中开发了我的应用程序。我尝试提交它,但在看到该错误后,我想也许我应该尝试使用非测试版 Xcode 提交它。顺便说一下,这里是错误:
So I went back into Xcode 6.3, the not beta Xcode and tried submitting again. It did the same thing! I then, still in Xcode 6.3, created another projects and just copied and pasted my code into a project that was not made in beta. I kept the same Bundle ID and everything.
所以我回到 Xcode 6.3,非测试版 Xcode 并尝试再次提交。它做了同样的事情!然后,我仍然在 Xcode 6.3 中创建了另一个项目,然后将我的代码复制并粘贴到一个非测试版的项目中。我保留了相同的 Bundle ID 和所有内容。
I still got the same result. So I have no idea what to do! I've been working on this for a whole day now and the Apple Watch is released in 5 days and I CAN'T MISS THAT!!! So PLEASE help!
我仍然得到相同的结果。所以我不知道该怎么办!我已经为此工作了一整天,Apple Watch 将在 5 天内发布,我不能错过!!!所以请帮忙!
I have tried:
我试过了:
Restarting both Beta Xcode and Normal Xcode
重新启动 Beta Xcode 和普通 Xcode
Logging out and logging back in again (on Mac desktop I mean)
注销并重新登录(我的意思是在 Mac 桌面上)
Doing the normal Developer Portal mumbo jumbo with regenerating the provisioning profile
通过重新生成配置文件来执行正常的开发人员门户笨拙的工作
Creating new project with same code
使用相同的代码创建新项目
PLEASE help! I thank you in advance!
请帮忙!我提前谢谢你!
回答by Oliver Pearmain
I got a similar error when attempting to submit, as below...
我在尝试提交时遇到了类似的错误,如下所示...
No matching provisioning profiles found for "Applications/yourapp.app"
None of the valid provisioning profiles allowed the specified entitlements:
beta-reports-active, com.apple.developer.ubiquity-kvstore-identifier.com,
com.apple.security.application-groups, com.apple.developer.ubiquity-container-identifiers
Short Answer:
简答:
Remove and re-install your provisioining profiles
删除并重新安装您的配置文件
Long Answer:
长答案:
When our project is built the appropriate provisioning profiles are installed automatically simply by being copied into the ~/Library/MobileDevice/Provisioning Profiles
directory.
构建我们的项目时,只需将适当的配置文件复制到~/Library/MobileDevice/Provisioning Profiles
目录中即可自动安装。
When the problem occurred I could see that the correct provisioning profiles existed in ~/Library/MobileDevice/Provisioning Profiles
HOWEVER when I opened the 'iPhone Configuration Utility' Mac application the appropriate provisioning profiles were NOT appearing (which I guess is an indication that they aren't properly installed, maybe coz they're corrupted or something)
当问题发生时,我可以看到正确的配置文件存在,~/Library/MobileDevice/Provisioning Profiles
但是当我打开“iPhone 配置实用程序”Mac 应用程序时,没有出现相应的配置文件(我猜这表明它们没有正确安装,可能是因为它们已损坏或什么的)
I have no idea how it got iteslf in this state but I was able to fix by deleting the existing files in the ~/Library/MobileDevice/Provisioning Profiles
directory, re-building the app so that the provisioning profiles were copied back into the directory forcing them to be reinstalled.
我不知道它是如何进入这种状态的,但我能够通过删除~/Library/MobileDevice/Provisioning Profiles
目录中的现有文件来修复,重新构建应用程序,以便将配置文件复制回目录,强制重新安装它们。
The provisioning profiles then became visible in iPhone Configuration Utiltiy and when submitting to the App Store this error no longer appeared.
配置文件随后在 iPhone Configuration Utiltiy 中可见,当提交到 App Store 时,此错误不再出现。