无效权利 iOS SDK 4.1
自从升级到 4.1 SDK 以来，当用户尝试安装 Ad-Hoc 版本时，我的权利不再有效。我们很久以前就遇到了这个问题，并通过向项目添加带有 get-task-allow = false 键的 Entitlements.plist 文件来解决它。
我认为除了将 Base SDK 升级到“iOS Device 4.1”之外，我没有更改项目配置中的任何内容。我还尝试删除并创建新的权利文件，但没有成功。
Ever since upgrading to the 4.1 SDK my Entitlements are no longer valid when users try to install the Ad-Hoc builds. We originally had this issue a long time ago and and solved it by adding to the project an Entitlements.plist file with a get-task-allow = false key.
I don't think I've changed anything in the project configuration except upgrade the Base SDK to "iOS Device 4.1". I've also tried removing and creating a new entitlements file with no luck.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
以下是有效的权利文件屏幕截图：
项目设置中的
Code Signing Entitlements键应为空白。Here's a working Entitlements file screenshot:
The
Code Signing Entitlementskey in the project settings should be blank.确保目标和项目的代码签名身份设置相同。
通过其他 iTunes（而不是开发 Mac 上的 iTunes）进行安装时，我遇到了“签名者无效”错误的问题。很奇怪，但就这样吧。
通过右键单击左侧菜单中目标下的应用程序名称并“获取信息”->构建来达到目标
检查所有三个配置，调试/发布/临时它们不一定相同，但它们必须与项目中的相同（目标：调试为项目：调试等），这是通过使用顶部菜单实现的， “项目”->编辑项目设置->构建
所有三个匹配使我的临时构建再次工作......在经历了很多头痛和头发拉扯之后。希望这有帮助。 :)
Be sure that your setting for code signing identity is the same for Target and Project.
I had a problem of getting "Signer is not valid" error when installing through other iTunes than the one on the development mac. Very odd, but there you go.
Target is reached by right-clicking your app name under targets in the left menu and 'get info'->build
check all three configurations, debug/release/ad hoc they are not necessarily the same, but they have to be the same as in Project (target:debug as project:debug and so on), which is reached by using the top menu, "Project"->edit project settings->build
Having all three matching up made my ad hoc builds work again... after much headache and hair pulling. Hope this helps. :)
尝试撤销您的 Ad Hoc 移动配置文件并重新生成它。我知道，听起来有点老套，但我在构建签名方面遇到了许多问题，我必须通过删除所有内容并从头开始来解决这些问题。
Try revoking your Ad Hoc mobile provisioning profile and regenerating it. Sounds a bit hacky, I know, but I've had a number of issues with build signing that I had to resolve by nuking everything and starting over from scratch.
如果您使用的是开发配置文件，则必须将权利的值设置为 true。但如果您使用的是分发配置文件，则该值应该为 false。
我尝试过这个，它对我有用。
If you are using Development profile then you have to set the value of the Entitlement to true. But if you are using Distribution profile then the value should be false.
I tried this and it worked for me.
在 Mucho Frustrationado 之后，我终于（在该线程的帮助下）让我的应用程序再次运行！ :)
感谢大家的建议，尤其是 Nicki！
我的情况是，我的 3GS 上有一个应用程序正在运行，我把它搁置了几周，当我回到它时，我想起我遇到了麻烦。我只是想在手机上获取调试版本，但遇到了它开始加载的情况（您会看到 Default.png），然后它就会退出。调试器刚刚说：
启动远程程序时出错：无法获取进程 532 的任务。
启动远程程序时出错：无法获取进程 532 的任务。
正在调试的程序没有运行。
正在调试的程序没有运行。
我经历了整个权利泥潭，最后，在撤销我的所有证书（通过钥匙串访问）并重新创建我的所有配置文件、开发人员证书等之后，以及今天的步骤，围绕着各种搞砸的版本值我的项目和目标构建设置。
今天，我的最后一个难题是按照 Nicki 的描述，理清所有版本和代码签名内容。确保没有留下“gremlin”设置（您可能在拔头发时插入的值），检查项目和目标构建中的版本匹配（您要发布的基础 SDK），检查权利（我必须手动分配我的，因为有多个分发配置文件，并且 Xcode 猜错了），交叉你的眼睛，然后在你的设备上构建并运行。
再次感谢大家！希望这个小花絮可以帮助其他人将这些点联系起来。 :)
再见，
-Jei。
After Mucho Frustrationado, I finally (with the help of this thread) got my app working again! :)
Thanks for the tips everyone, especially Nicki!
My situation was that I had an app working on my 3GS, set it aside for a few weeks and when I came back to it, I remembered that I was having trouble. I was merely trying to get a Debug version on my phone, but ran into the situation where it would start to load (you'd catch a glimpse of the Default.png), and then it would quit. The Debugger just said:
Error launching remote program: failed to get the task for process 532.
Error launching remote program: failed to get the task for process 532.
The program being debugged is not being run.
The program being debugged is not being run.
I went through the whole Entitlements quaqmire, and finally, after revoking all my certificates (through Keychain Access) and re-creating all my Provisioning Profiles, Developer Certificate, et al, and today's step which revolved around all kinds of screwed up version values in my Project and Target Build settings.
Today, my last piece of the puzzle, was to get all the versions and Code Signing stuff straightened out as Nicki described. Make sure no "gremlin" settings (values you may have plugged while pulling your hair out) are left behind, check the versions match (the Base SDK you're publishing for) in Project and Target Build, check the Entitlements (I had to manually assign mine as there were multiple Distribution profiles, and Xcode guessed wrong), cross your eyes, and Build and Run on your device.
Thanks again everyone! Hope this little tidbit helps someone else connect the dots. :)
Ciao,
-Jei.
Xcode 4 中的 Ad Hoc 构建不再需要代码签名权利 - 请参阅 Apple 技术说明 TN2250
Code signing entitlements are no longer necessary for Ad Hoc builds in Xcode 4 - see details notes in Apple Technical Note TN2250