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

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

问题描述

我已经与这个问题抗争了好几天了,现在正想用头撞墙,让自己摆脱代码签名/应用提交的痛苦.

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.

我有一个应用程序已经提交到应用商店并且接受没有问题(1.0.0 版).我能够通过应用程序加载器使用 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 中的捆绑标识符设置为com.myCompany.myApp"时,我可以根据 AppStore Distribution 条款成功构建我的应用程序.但是,当我尝试通过 Organizer 验证/提交构建时,我收到错误消息,指出捆绑标识符:com.myCompany.myApp 与先前的捆绑标识符 ABC123XYZ1.com.myCompany.myApp 不同".显然,当我第一次通过 iTunes 连接提交我的应用程序时,我使用了完整的 (AppId).BundleIdentifer 语法.我已经通过在 iTunes 连接中查看捆绑 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.

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

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.

我已经尝试了所有我在互联网上阅读的关于这两个错误的所有内容,但没有解决问题.我处于 catch 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!

推荐答案

因此,在等待 iTunes 团队的答复 2 个月后,一直没有得到答复,我找到了解决此问题的方法并上传了我的应用程序.关键是使捆绑标识符与在 iTunesConnect 中注册的捆绑 ID 匹配.在这种情况下,iTunesConnect 中的捆绑 ID 的格式为 1234567890.com.companyname.appname.当我第一次创建我的应用程序时,我已经包含了捆绑种子 ID,当在 iTunesConnect 中创建应用程序时,我的研究不应该包含它.

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天全站免登陆