Xcode 3.2的代码签名错误 [英] Code sign error with Xcode 3.2

问题描述

在升级到iPhone OS 3.1和Xcode 3.2之前，我有一个完全正常工作的构建环境。现在，当我尝试进行构建时，我得到以下内容：

I had a fully working build environment before upgrading to iPhone OS 3.1 and Xcode 3.2. Now when I try to do a build, I get the following:

代码签名错误：供应配置文件'FooApp test'指定应用程序标识符'no.fooapp.iphoneapp'与当前设置'TGECMYZ3VK.no.fooapp.iphoneapp'不匹配

Code Sign error: Provisioning profile 'FooApp test' specifies the Application Identifier 'no.fooapp.iphoneapp' which doesn't match the current setting 'TGECMYZ3VK.no.fooapp.iphoneapp'

问题是Xcode以某种方式设法认为FooApp Test配置文件指定了应用程序标识符no.fooapp.iphoneapp，但事实并非如此。

The problem is that Xcode somehow manages to think that the "FooApp Test" provisioning profile specifies the Application Identifier "no.fooapp.iphoneapp", but this is not the case.

在组织者（以及iPhone开发人员门户网站）的应用程序标识符被正确地视为TGECMYZ3VK.no.fooapp.iphoneapp。

In the Organizer (and in the iPhone developer portal website) the app identifier is correctly seen as 'TGECMYZ3VK.no.fooapp.iphoneapp'.

此外，在设置配置文件时在项目级别的构建选项中，Xcode正确识别应用程序标识符，但是当我转到目标时，我无法选择任何有效的配置文件。

Also, when setting the provisioning profile in the build options at the project level, Xcode correctly identifies the app identifier, but when I go to the target, I'm unable to select any valid provisioning profile.

什么可能会导致这个问题吗？

What could be causing this problem?

更新：我试图创造一个新的配置文件，但仍然没有运气。我还尝试将Info.plist中标识的应用程序更改为no.fooapp.iphoneapp。构建成功，但现在我从管理器收到错误：

Update: I've tried to create a new provisioning profile, but still no luck. I also tried simply changing the app identified in Info.plist to just "no.fooapp.iphoneapp". The build succeeds, but now I get an error from the Organizer:

可执行文件使用无效的权利签名。应用程序的代码签名权利文件中指定的权利与您的供应配置文件中指定的权利不匹配。 （0xE8008016）。

The executable was signed with invalid entitlements. The entitlements specified in your application's Code Signing Entitlements file do not match those specified in your provisioning profile. (0xE8008016).

这似乎是合理的，因为配置文件仍然具有TGECMYZ3VK.no.fooapp.iphoneapp应用程序标识符。

This seems reasonable, as the provisioning profile still has the "TGECMYZ3VK.no.fooapp.iphoneapp" application identifier.

我还仔细检查了所有证书在钥匙串中是否有效。

I also double checked that all certiicates are valid in the Keychain.

所以我的问题是我怎么做获取Xcode以查看正确的应用程序标识符？

So my question is how I can get Xcode to see the correct application identifier?

更新：如下所述，解决问题的方法是删除所有配置文件，证书等，制作新证书/ profiles并再次安装它们。如果有人有任何其他解决方案，他们将受到欢迎。 ：）

UPDATE: As noted below, what seems to fix the problem is deleting all provisioning profiles, certificates, etc., making new certificates / profiles and installing them again. If anyone has any other solutions, they would be welcome. :)

推荐答案

好吧，就像很多这些代码签名问题一样，删除所有配置文件，证书等等，并且再次撤销和生成所有内容，结果证明了这一点。我甚至创建了一个新的包标识符，应用程序标识符等，现在AdHoc发行版再次正常运行。

Well, as seems to be the case with a lot of these code signing issues, deleting all provisioning profiles, certificates, etc. and revoking and generating everything all over again turned out to do the trick. I even created a new bundle identifier, app identifier, etc., and now AdHoc distribution is working again.

这篇关于Xcode 3.2的代码签名错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！