xcode 签名（调试）不包括 beta-reports-active 权利

Signing (Debug) doesn't include the beta-reports-active entitlement

提问by skyylex

During the try to setup signing settings of Xcode 8, I've got the following error for the development provision profile:

在尝试设置 Xcode 8 的签名设置期间，我的开发配置文件出现以下错误：

Provisioning profile "XXX" doesn't include the beta-reports-active entitlement.

配置文件“XXX”不包括 beta-reports-active 权利。

recreation of the provision profiles doesn't help. I'm not quite sure if this type of profile needs beta-reports-active settings at all, as I saw other issues only AppStore profiles should use these settings.

重新创建配置文件无济于事。我不太确定这种类型的配置文件是否需要 beta-reports-active 设置，因为我看到其他问题只有 AppStore 配置文件应该使用这些设置。

I will appreciate any help

我将不胜感激任何帮助

UPDATE:

更新：

AdHoc provision profile has the same error, however AppStore provision profile works fine for Release.

AdHoc 配置文件有同样的错误，但 AppStore 配置文件适用于 Release。

回答by Rajshekhar Sahu

I was getting this error while trying to make AdHoc distribution build from Xcode 9.0. By mistake I choose different provision profile in Signing(Distribution) and Signing(Release). As I made same provision for both, the error gone.

我在尝试从 Xcode 9.0 构建 AdHoc 发行版时遇到此错误。我错误地在签名（分发）和签名（发布）中选择了不同的配置文件。由于我为两者做了相同的规定，错误消失了。

Hope this will help.

希望这会有所帮助。

Thanks.

谢谢。

回答by RomanN

I had the same error when was trying to export AdHoc build (though AppStore worked well).

我在尝试导出 AdHoc 构建时遇到了同样的错误（尽管 AppStore 运行良好）。

The problem was solved by switching Provisioning Profile in project settings general tab, from AppStore config to AdHoc and archiving again.

通过在项目设置常规选项卡中切换 Provisioning Profile，从 AppStore 配置到 AdHoc 并再次存档，解决了该问题。

回答by Ketan Patel

I had the same error when I was trying to export AdHoc build.

我在尝试导出 AdHoc 构建时遇到了同样的错误。

The problem was resolved by change Provisioning Profile in project settings general tab, from AppStore config to AdHoc and archiving again it works for me.

通过在项目设置常规选项卡中更改 Provisioning Profile，从 AppStore 配置到 AdHoc 并再次归档它解决了这个问题，它对我有用。

回答by skyylex

I had set entitlements with beta-reports-active for debug and release configuration. After removal of the path to Debug entitlements error disappeared.

我已经为调试和发布配置设置了 beta-reports-active 的权利。删除调试权限的路径后，错误消失了。

As written in the Apple documentation:

正如 Apple 文档中所写：

https://developer.apple.com/library/content/qa/qa1830/_index.html

https://developer.apple.com/library/content/qa/qa1830/_index.html

beta-reports-active is a new entitlement added to App Store profiles in September 2014 to allow App Store code signed builds to be tested using iTunes Connect

beta-reports-active 是 2014 年 9 月添加到 App Store 配置文件中的一项新权利，允许使用 iTunes Connect 测试 App Store 代码签名版本

So it should not be set in the other builds.

所以它不应该在其他版本中设置。

回答by Nekto

So the reason it happens is because when archiving xcodebuildis packaging provisioning profiles specified for the build configuration and updates .xcentfor all binaries in IntermediateBuildFilesPathto match whatever is specified in those profiles.

所以它发生的原因是因为归档时xcodebuild打包为构建配置指定的配置.xcent文件和所有二进制文件的更新，IntermediateBuildFilesPath以匹配这些配置文件中指定的内容。

For example, if you have multiple configurations, like beta and release, most likely you are specifying beta (ad-hoc w/o beta-reports-activein them) provisioning profiles for one and release (app-store w/ beta-reports-activein them) provisioning profiles for another one.

例如，如果您有多个配置，例如 beta 和 release，很可能您正在beta-reports-active为其中一个指定 beta（其中不包含临时）配置文件，并为另一个指定发布（其中包含应用商店beta-reports-active）配置文件.

Then after you archived beta configuration, you will have an option to export archive for both - beta and release distribution (website and TestFlight) and xcodebuildwon't throw this error because used provisioning profiles are missing beta-reports-activeand when it will sign for App Store distribution (TestFlight, for example) it will pick up correct profiles (assuming you explicitly specified them in a plist passed to -exportOptionsPlist).

然后在您存档 Beta 配置后，您将可以选择导出 Beta 版和发行版（网站和 TestFlight）的存档，并且xcodebuild不会抛出此错误，因为缺少使用的配置文件beta-reports-active以及何时签署 App Store 分发版（例如，TestFlight）它将选择正确的配置文件（假设您在传递给 的 plist 中明确指定了它们-exportOptionsPlist）。

Now when you archived release configuration, the story is different. Now xcodebuild packaged provisioning profiles with a beta-reports-activeflag and xcodebuild won't allow you to export (resign) with beta provisioning profiles for whatever reason. I think this is an actual xcodebuild bug.

现在，当您归档发布配置时，情况就不同了。现在 xcodebuild 打包了带有beta-reports-active标志的配置文件，无论出于何种原因，xcodebuild 都不允许您使用 beta 配置文件导出（退出）。我认为这是一个实际的 xcodebuild 错误。

Assuming all my assumptions and understanding of the error are correct, one should always use beta provisioning profiles when archiving, no matter which configuration, but export with a proper profiles later.

假设我的所有假设和对错误的理解都是正确的，归档时应始终使用 beta 配置文件，无论哪种配置，但稍后使用适当的配置文件导出。

回答by juanram0n

In My case, using xcode 9.2 the solution was using old build method, not the new one to archive my project. Probably is the thing on Apple xCode that's not polished at all, it seems neither in 9.3 but I don't know if you can select method in 9.3. I read that it was solved on 9.4.

在我的情况下，使用 xcode 9.2 的解决方案是使用旧的构建方法，而不是新的方法来归档我的项目。可能是 Apple xCode 上根本没有打磨的东西，在 9.3 中似乎都没有，但我不知道您是否可以在 9.3 中选择方法。我读到它已在 9.4 上解决。

回答by HDdeveloper

No matching provisioning profiles found for "your.app" 
None of the valid provisioning profiles allowed the specified 
entitlements: beta-reports-active.

beta-reports-active is a new entitlement added to App Store profiles Apple doc state.

beta-reports-active 是添加到 App Store 配置文件Apple 文档状态的新权利 。

NOTE: "Validate" and "Submit" features on the Xcode Organizer Archives tab require an App Store provisioning profile. Therefore, Validate or Submit is not intended to be used with Development, Ad Hoc or Enterprise builds. Ad Hoc or Enterprise distributions should skip straight to Export.

注意：Xcode Organizer Archives 选项卡上的“验证”和“提交”功能需要 App Store 配置文件。因此，验证或提交不适用于开发、临时或企业构建。Ad Hoc 或 Enterprise 发行版应直接跳至导出。

1. On the Certs IDs & Profiles website > Provisioning Profiles page, click the App Store profile. Click 'Edit' Click 'Generate' To create a new App Store profile, click the "+" button on the Distribution Provisioning Profiles page.

2. After creating or updating your App Store profile, do one of the following to install the updated profile in Xcode:

3. Click 'Download' and drag/drop the provisioning profile onto the Xcode icon on the dock Click '?' on Xcode > Preferences > Accounts > (your account) > View Details pane

1. 在证书 ID 和配置文件网站 > 配置配置文件页面上，单击 App Store 配置文件。单击“编辑” 单击“生成” 要创建新的 App Store 配置文件，请单击分发供应配置文件页面上的“+”按钮。

2. 创建或更新您的 App Store 配置文件后，执行以下操作之一以在 Xcode 中安装更新的配置文件：

3. 单击“下载”并将配置文件拖放到 Dock 上的 Xcode 图标上单击“？” 在 Xcode > Preferences > Accounts > (your account) > View Details 面板

In my case, it happened when my teammate created a new distribution certificate and provision profile. It worked fine when I deleted existing invalid certificates(shown with red error mark) from "Keychain Access" Also, check if release and debug schemes are using respective signing identities.

就我而言，它发生在我的队友创建新的分发证书和配置文件时。当我从“钥匙串访问”中删除现有的无效证书（显示为红色错误标记）时，它工作正常此外，检查发布和调试方案是否使用各自的签名身份。

回答by Yu Siqi

Let me tell you the correct answer. Xcode archive with Release packages by default, when you export development version with Release package will show thie error. We should archive Debug package changing this in schemes option and then export development version. KO!^_^

让我告诉你正确的答案。默认情况下，Xcode 存档带有 Release 包，当您导出带有 Release 包的开发版本时会显示错误。我们应该在方案选项中存档调试包，然后导出开发版本。好！^_^

回答by Abhisek Singh

Regenerate your Provisional profile will solve this problem. To regenerate your Provisional Profile follow the following step.

重新生成您的临时配置文件将解决此问题。要重新生成您的临时配置文件，请按照以下步骤操作。

On the Certs IDs & Profiles website > Provisioning Profilespage, click the App Store profile.

在证书 ID 和配置文件网站 > 配置配置文件页面上，单击 App Store 配置文件。

Click 'Edit'

点击“编辑”

Click 'Generate'

点击“生成”

Rebuild your app using newly created provisional profile and Archive it. Visit link

使用新创建的临时配置文件重建您的应用程序并将其存档。访问链接