ios 应用程序“不包含正确的测试版权利”

App "does not contain the correct beta entitlement"

提问by Aaron Wojnowski

I submitted an application for review and I notice that the build that I submitted has an issue associated with it saying that Build 168 does not contain the correct beta entitlement.I wasn't able to find information on this error anywhere. What does it mean and will it inhibit the review process? My app was submitted today with Xcode 5.1.1 for iOS 7 (not the Xcode GM). Perhaps this relates to Testflight?

我提交了一份申请以供，但我注意到我提交的构建有一个与之相关的问题，说Build 168 does not contain the correct beta entitlement.我无法在任何地方找到有关此错误的信息。它是什么意思，它会抑制过程吗？我的应用程序今天与 iOS 7 的 Xcode 5.1.1（不是 Xcode GM）一起提交。也许这与Testflight有关？

采纳答案by Nitin

Please regenerate your provisioning profile. It will Fix this problem it's because the missing entitlement is now there beta-reports-active = 1

请重新生成您的配置文件。它将解决这个问题，因为缺少的权利现在在那里beta-reports-active = 1

After creating the new provisioning profile, make sure the entitlement is there.

创建新的配置文件后，请确保权利存在。

Here is how it should look like when you click in Organizer "Export.." -> "Save for iOS App Store Deployment":

当您在管理器中单击“导出..”->“保存用于 iOS App Store 部署”时，它应该是什么样子：

回答by Ryan Romanchuk

Apple gave us a little surprise yesterday without telling us. There is a new entitlement that is added when you regenerate your distribution certificate. When you regenerate, as others said, it should fix your problem. It's not due to magic though, it's because the missing entitlement is now there beta-reports-active = 1

苹果昨天在没有告诉我们的情况下给了我们一个小惊喜。重新生成分发证书时会添加一项新权利。正如其他人所说，当您重生时，它应该可以解决您的问题。不过，这不是因为魔法，而是因为缺少的权利现在就在那里beta-reports-active = 1

Once you download your new provisioning profile, make sure the entitlement is there, rebuild your IPA and this warning should finally go away. If you manage your own Entitlements.plistbe sure to include this new key.

下载新的配置文件后，请确保权利在那里，重建您的 IPA，此警告最终应该会消失。如果您自己管理，请Entitlements.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">
    <dict>
        <key>aps-environment</key>
        <string>production</string>
        <key>get-task-allow</key>
        <false/>
        <key>beta-reports-active</key>
        <true/>
        <key>application-identifer</key>
        <string>bkahblahblah</string>
    </dict>
</plist>

回答by Maciek Czarnik

Yes, you need to recreate provisioning profile and one more important thing is that you need to provision your app with App Store distribution provisioning profile.

是的，您需要重新创建配置文件，更重要的一件事是您需要使用 App Store 分发配置文件来配置您的应用程序。

Here is how it should look like when you click in Organizer "Export..." -> "Save for iOS App Store Deployment":

当您在管理器中单击“导出...”->“保存用于 iOS App Store 部署”时，它应该是什么样子：

You can also convert .mobileprovision file to .xml with that command to see if there really is a beta-reports-activekey in your entitlements.

您还可以使用该命令将 .mobileprovision 文件转换为 .xml，以查看beta-reports-active您的权利中是否确实存在密钥。

security cms -D -i YourProfile.mobileprovision > YourProfile.xml

security cms -D -i YourProfile.mobileprovision > YourProfile.xml

回答by Oren

You need to recreate provisioning profile (as everyone suggested), however you also need to distribute the IPA with an "App Store" distribution profile. If you're used to the old TestFlight distribution methods, you're probably signing the package with an "Ad Hoc" profile instead.

您需要重新创建配置文件（正如每个人所建议的），但是您还需要使用“App Store”分发配置文件分发 IPA。如果您习惯了旧的 TestFlight 分发方法，则您可能会使用“Ad Hoc”配置文件对包进行签名。

回答by Zaldy

There are two step here:

这里有两个步骤：

1. Regenerate your provisioning profiles. Especially the AppStore provisioning profile to make sure the beta entitlement is there.
2. Archive and export your build by selecting the option "Save for iOS App Store Deployment"

1. 重新生成您的配置文件。尤其是 AppStore 配置文件，以确保 Beta 权限在那里。
2. 通过选择选项“保存为 iOS App Store 部署”来存档和导出您的构建

Some of the mistakes comes from exporting the archive using the AdHoc deployment.

一些错误来自使用 AdHoc 部署导出存档。

I bet Apple might remove AdHoc deployment in the future since TestFlight Beta Testing using AppStore builds serves the purpose.

我敢打赌，Apple 将来可能会删除 AdHoc 部署，因为使用 AppStore 构建的 TestFlight Beta 测试可以达到目的。

Hope this helps.

希望这可以帮助。

回答by Etienne

For all it's worth I was using the Application Loader to upload the app and I never managed to get it to work (Application loader version 3.0 (620)). Once I tried using xCode via the Archive method things worked great. You can also tell if the Beta entitlement is present before submission.

尽管如此，我使用 Application Loader 上传应用程序是值得的，但我从未设法让它工作（应用程序加载器版本 3.0 (620)）。一旦我尝试通过 Archive 方法使用 xCode，一切都很好。您还可以在提交前判断 Beta 权限是否存在。

回答by saemitang

I just tried submitting a new build of my app using Xcode 6. It complains about the invalid provisioning profiles that I have for the built app. So I regenerated the provisioning profiles at Apple Developer website and import them in Xcode 6. Uploaded the new built binary using the new provisioning profiles and submitted for review. The new provisioning profiles includes beta entitlements that I think iTunes Connect is complaining about. Hopefully it will not complain about the beta entitlements later.

我刚刚尝试使用 Xcode 6 提交我的应用程序的新版本。它抱怨我为构建的应用程序所拥有的配置文件无效。因此，我在 Apple Developer 网站上重新生成了配置文件，并将它们导入到 Xcode 6 中。使用新的配置文件上传了新构建的二进制文件并提交以供审核。新的配置文件包括我认为 iTunes Connect 抱怨的 beta 权限。希望它以后不会抱怨测试版权利。

回答by Chris

Regenerate all your provisioning profiles, fixes the problem 100%

重新生成所有配置文件，100% 解决问题

回答by Raghav

I was also facing same issue but suddenly the message in the itunesconnect got changed to "To use TestFlight Beta Testing, this build must contain the correct beta entitlement. For more information, see the(Link)" in the prerelease section.

我也遇到了同样的问题，但突然间 itunesconnect 中的消息更改为“要使用 TestFlight Beta 测试，此版本必须包含正确的 Beta 授权。有关更多信息，请参阅预发布部分中的（链接）”。

With TestFlight Beta Testing, you can distribute your prerelease builds to testers to collect feedback and prepare your app for release in the App Store. TestFlight Beta Testing is optional; you can submit your app for review without using it.

通过 TestFlight Beta 测试，您可以将预发布版本分发给测试人员以收集反馈并准备您的应用程序以在 App Store 中发布。TestFlight Beta 测试是可选的；您可以在不使用应用的情况下提交应用以供审核。

Ref: here

参考：这里

回答by NaXir

I got same issue. After regenerating provisioning profiles I again got same issue. Then I uploaded binary via Xcode and it solved the issue.

我有同样的问题。重新生成配置文件后，我再次遇到了同样的问题。然后我通过 Xcode 上传了二进制文件，它解决了这个问题。

It seems like issue is with Application Loader. Use Xcodeto uploadthe binary.

似乎问题出在Application Loader 上。使用Xcode中来上传二进制文件。