代码签名错误:无法找到与应用程序的标识符匹配的有效供应配置文件 [英] Code Sign error: a valid provisioning profile matching the application's Identifier ... could not be found

查看:151
本文介绍了代码签名错误:无法找到与应用程序的标识符匹配的有效供应配置文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我几天来一直在争论这个问题,并且即将击败我的头,让自己摆脱我的代码签名/应用程序提交的痛苦。

I have been fighting this issue for days now and about to beat my head against the wall and put myself out of my code signing/app submission misery.

I有一个已经提交到应用程序商店的应用程序并且没有接受任何问题(版本1.0.0)。我能够通过Application Loader使用XCode 3.2.4和iOS 4.1发布第一次更新(版本1.0.1),稍微尝试一次错误。现在我在XCode 3.2.5和iOS 4.2上,并尝试通过XCode Organizer发布更新(版本1.0.2)。

I have an application that has been submitted to the app store and accepted no problems (ver 1.0.0). I was able to publish the first update (ver 1.0.1) with a little bit of trial an error using XCode 3.2.4 and iOS 4.1 via Application Loader. Now I am on XCode 3.2.5 and iOS 4.2 and am trying to publish an update (ver 1.0.2) via XCode Organizer.

我可以成功构建我的应用程序我在info.plist中将我的Bundle Identifier设置为com.myCompany.myApp时的AppStore Distribution配置。但是当我尝试通过Organizer验证/提交构建时,我得到并且错误声明Bundle Identifier:com.myCompany.myApp与先前的bundle标识符ABC123XYZ1.com.myCompany.myApp不同。显然,当我第一次通过iTunes连接提交我的应用程序时,我使用了完整的( AppId )。 BundleIdentifer 语法。我已通过查看iTunes连接中的Bundle ID验证了这一点。

I can successfully build my application against the AppStore Distribution provision when I set my Bundle Identifier in the info.plist to "com.myCompany.myApp". But when I try to Validate/Submit the build via Organizer I get and error stating "Bundle Identifier: com.myCompany.myApp differs from prior bundle identifier ABC123XYZ1.com.myCompany.myApp". Apparently when I first submitted my app via iTunes connect I used the full (AppId).BundleIdentifer syntax. I have verified this by viewing the Bundle ID in iTunes connect.

因此,从逻辑上讲,我在AppId前缀中添加了Info.plist文件中的包标识符。当我这样做并尝试再次构建时,我收到代码签名错误:无法找到与应用程序的标识符匹配的有效配置文件...。并且构建失败。

So, logically, I added in the AppId prefix to the bundle identifier in the Info.plist file. When I do this and try to build again, I get "Code Sign error: a valid provisioning profile matching the application's Identifier ... could not be found." and the build fails.

我已经尝试了所有关于这两个错误的互联网上的所有内容,但没有解决问题。我陷入困境22。我无法在捆绑标识符中使用AppID前缀构建应用程序,如果没有它,我无法将其提交给iTunesConnect。此外,当尝试使用Application Loader上传应用程序时,会发生iTunesConnect错误。

I have tried everything I have read everything on the internet regarding these two errors with no resolution to the problem. I am in a catch 22 situation. I can't build the app with the AppID prefix in the bundle identifer and I can't submit it to iTunesConnect without it. Also, the iTunesConnect error occurs when trying to use Application Loader to upload the app.

我准备将我的第一个孩子提供给任何可以帮助我摆脱困境的人代码签名/应用程序提交地狱!

I am prepared to offer my first born to anyone who can help me get out of this code signing/app submission hell!

推荐答案

所以等了2个月的iTunes团队的答案,从未来过,我已经找到解决这个问题的方法并让我的应用程序上传。关键是使包标识符与在iTunesConnect中注册的包ID匹配。在这种情况下,iTunesConnect中的软件包ID为1234567890.com.companyname.appname。在我第一次创建应用程序的时候,我已经包含了捆绑种子ID,当我在iTunesConnect中创建应用程序时,该种子ID不应包含在我的研究中。

So after waiting 2 months for an answer from the iTunes team, which never came, I have figured out a way around this issue and got my app to upload. The key is to make the bundle identifier match the bundle id that is registered in iTunesConnect. In this case the bundle id in iTunesConnect was in the form of 1234567890.com.companyname.appname. Some how when I first created my app I had included the bundle seed id which from my research should not have been included when the app was created in iTunesConnect.

要解决此问题,我在配置门户中以1234567890.1234567890.com.companyname.appname的形式创建了一个新的App ID,然后创建了一个新的分发移动设备在这个新的AppID上。我在xCode Organizer中下载并安装了移动设备。在我的xCode项目的info.plist中,我将包标识符设置为1234567890.com.companyname.appname。这允许xCode将移动配置与info.plist中的指定包标识符进行匹配,并使用与iTunesConnect中的包ID匹配的包标识符成功构建并签署我的应用程序。在组织者中,我能够成功验证并上传应用程序。

To resolve the issue, I created a new App ID in the provisioning portal in the form of 1234567890.1234567890.com.companyname.appname and then created a new distribution mobile provision based on this new AppID. I downloaded and installed the mobile provision in xCode Organizer. In the info.plist of my xCode project I set the bundle identifier to 1234567890.com.companyname.appname. This allowed xCode to match the mobile provision to the specified bundle identifier in the info.plist and successfully build and sign my app with a bundle identifier that matched the bundle id in iTunesConnect. In organizer I was able to validate and upload the app successfully.

这篇关于代码签名错误:无法找到与应用程序的标识符匹配的有效供应配置文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆