xcode 尝试构建非临时版本时出现 Entitlements.plist 错误？

Entitlements.plist error when trying to build non ad-hoc versions?

提问by adonji

I searched all around for an answer but no luck....

我四处寻找答案，但没有运气......

I successfully built an ad-hoc version of this app, but now when i try to build for debug, release, or regular distribution i get the build error:

我成功构建了此应用程序的临时版本，但是现在当我尝试为调试、发布或常规分发构建时，出现构建错误：

"CodeSign error: The entitlements file '/Users/Dropbox/myApp/Entitlements.plist' is missing"

“CodeSign 错误：缺少权利文件‘/Users/Dropbox/myApp/Entitlements.plist’”

the thing is
a) The entitlements.plist file is sitting right there in the resources folder
b) That isn't even the correct path to the xcode project folder.
c) I removed the key from the project settings> build> code signing entitlements, so why is it even looking for the entitlements.plist?

问题是
a) entitlements.plist 文件就在资源文件夹中
b) 这甚至不是 xcode 项目文件夹的正确路径。
c) 我从项目设置> 构建> 代码签名权利中删除了密钥，那么它为什么还要寻找 entitlements.plist？

what is going on?? How can I get xcode to stop trying to find the entitlements file, I know it isnt even needed for the anything other than ad-hoc builds.

到底是怎么回事？？我怎样才能让 xcode 停止尝试查找权利文件，我知道它甚至不需要临时构建以外的任何东西。

回答by adonji

Thanks all, i think i figured it out. Hopefully this will help anyone else who runs into this:

谢谢大家，我想我想通了。希望这会帮助其他遇到此问题的人：

I ended up going into 'targets' and right-clicking 'get info' (or alternatively Project>Edit Active Target ) and the entitlement.plist is listed in the build tab there as well. I removed it there and in the project settings and issue solved.

我最终进入“目标”并右键单击“获取信息”（或者 Project>Edit Active Target），并且 entitlement.plist 也列在那里的构建选项卡中。我在那里和项目设置中将其删除并解决了问题。

Again, thanks all :)

再次感谢大家:)

回答by odukku

In my case what really helped out was : 1. Click the project just above the target. 2. Goto build settings 3. Change the code signing entity to the correct one .

就我而言，真正有帮助的是： 1. 单击目标正上方的项目。2. 转到构建设置 3. 将代码签名实体更改为正确的。

回答by amattn

99% you don't need Entitlements.plist. it's just a bad error message (possibly the worst and most misleading in all of Xcode)

99% 你不需要 Entitlements.plist。这只是一个糟糕的错误信息（可能是所有 Xcode 中最糟糕和最具误导性的）

Instead, re-download your provisioning profile.

相反，重新下载您的配置文件。

回答by Amit

Just a suggestion. Yes, removing Entitlements.plist from settings works. But most probably the path listed in the settings has changed, as it is an absolute path.

只是一个建议。是的，从设置中删除 Entitlements.plist 有效。但很可能设置中列出的路径已更改，因为它是绝对路径。

In my case it folder name had changed but framework was looking for the file in old path.

就我而言，它的文件夹名称已更改，但框架正在旧路径中查找该文件。

回答by fayaz

Tap on Targets => Summary => Entitlements => Check out "Use Entitlements File". This worked fine.

点击目标 => 摘要 => 权利 => 查看“使用权利文件”。这工作得很好。

回答by Simon Goldeen

A couple ideas:

几个想法：

1. Make sure that the build settings you are editing is the one for the build configuration you are building with.
2. I have found what works for me is to toggle the "get-task-allow" boolean when I build for development (true for development builds, false for ad-hoc).

1. 确保您正在编辑的构建设置与您正在构建的构建配置相符。
2. 我发现对我有用的是在我为开发构建时切换“get-task-allow”布尔值（对于开发构建为 true，对于临时构建为 false）。

I am pretty sure that if you have an entitlements plist in your project, it will try to use that unless another one is specified, so you might be able to have two entitlements plists and have your ad-hoc configuration point to one and your development configuration point to the other.

我很确定，如果您的项目中有一个权利 plist，它会尝试使用它，除非指定了另一个，因此您可以拥有两个权利 plist，并将您的临时配置指向一个，并且您的开发配置指向其他。

回答by Shauket Sheikh

I deleted code signing entitlements entry from build setting, after that my error gone and i am able to make archive without any issue.if you have no file entitlement.plist you should delete entry from build setting.

我从构建设置中删除了代码签名权利条目，之后我的错误消失了，我可以毫无问题地进行存档。如果您没有文件 entitlement.plist，您应该从构建设置中删除条目。