如何准备要提交给应用商店的应用?我* KEEP *收到代码签名错误? [英] How do i prepare an app for submittion to the app store? I *KEEP* getting code signing errors?

问题描述

如果不是一个错误，那就是另一个.如果不是那样，那是另外一回事了.我觉得我现在在项目中进行了很大的更改，只是想解决代码签名问题，而这一切都弄糟了.我按照字母上的说明操作并收到错误消息，例如当前的代码签名错误":"iPhone发行版"标识与任何配置文件中的任何标识都不匹配，或者我选择了"iPhone发行版"以外的其他选项(否配置文件当前匹配)"，例如团队配置配置文件:iPhone开发人员[我的名字](长号)"或"[我的名字]配置文件:iPhone开发人员:[我的名字](长号)"，我收到了错误消息权利文件'/Users/Me/Appfolder/Classes/Entitlements.plist'丢失，我在修复此问题的1个教程中将其删除.

If it's not one error, it's another. If it's not that, it's something else. I feel like i've changed so much in my project now just trying to work around the code signing thing that it's all messed up. I follow instructions to the letter and get errors, for example the current one of 'Code Sign error: The identity 'iPhone Distribution' doesn't match any identity in any profile', or if i choose anything other than 'iPhone Distribution (No profiles currently match)', such as 'Team provisioning profile: iPhone Developer [my name] (long number)' or '[my name] Profile: iPhone Developer: [my name] (long number)' i get an error of The entitlements file '/Users/Me/Appfolder/Classes/Entitlements.plist' is missing, which i deleted as a step in 1 tutorial to fixing this mess.

现在我完全不知所措了.它应该是文件">导出".甚至不应该有这种愚蠢的代码签名功能.如果这是为了防止黑客入侵，则无论如何黑客都可以通过它，从而使这一点无效.我好讨厌我希望有人能提供任何帮助吗?也许是使用笨拙的证书系统从头开始重新启动的指南?我只想上传我的应用程序，这就是我要做的.但是由于这个愚蠢的，复杂的流程很容易出错(顺便说一句，该公司以能够直截了当，简单明了，以废除废话而自豪)，所以我无法做到这一点.

I am totally at my wits end with this now. It should be File > Export. There shouldn't even be this stupid code signing feature. If it's to prevent hackers, hackers can get through it anyway so that nullifies the point. I'm so sick of it. I would appreciate any help with this that anybody could give? Maybe a guide to starting again from scratch with the stupid certificates system or something? I just want to upload my app, that's all i want to do. But because of this silly little complicated process which can so easily go wrong (by the way, made by the company who pride themselves on being straight forward and simple by cutting out the crap) i'm unable to do that.

推荐答案

我的问题的第一个来源-钥匙串中的重复私钥，来自Mobile Me同步和多个Mac拥有权.这是我建议一劳永逸解决此问题的方法. (的确如此-自从我完成了这项配置后，就已经可以想象到了.)

Number one source of my problems - duplicated private keys in the keychain, from Mobile Me syncing and multiple Mac ownership. Here's what I suggest to fix that problem once and for all. (Really - since I did this provisioning has been as easy as I can imagine it being.)

在所有Mac上转到钥匙串访问".删除所有公钥和私钥.生成一个新的证书请求，然后您应该只有一个公钥和私钥.通过双击钥匙串访问"来命名这对-狠狠地杀死所有其他钥匙！ (您不能像在Finder中进行操作一样重命名它，您必须通过双击打开窗口)我将其称为亚当·埃伯巴赫(Adam Eberbach)的Singleton私钥".导出该密钥对，然后将其导入到其他计算机上.永久保存它，但是当然不要与他人共享您的私钥.

Go to Keychain Access on all your Macs. Delete all your public and private keys. Generate a new certificate request and you should then have exactly one public and private key. NAME this pair by double-clicking in Keychain Access - ruthlessly kill all other keys! (you can't rename it like you do things in the Finder, you have to open the window by double clicking) I called mine "Adam Eberbach's Singleton Private Key". Export that key pair and then import it on your other machines. Keep it forever but of course don't share your private key with others.

由于删除所有这些密钥而发生的最糟糕的事情是不得不再次登录几个网站.我想知道是否还会有其他后果?

The worst thing that happened as a result of deleting all those keys was having to sign into a couple of websites again. I'd like to know if there could be other consequences?

拥有一对真正的密钥对后，请转到developer.apple.com并删除所有证书和置备配置文件.用您的一个真实密钥生成新证书.

Once you have your one true key pair, go to developer.apple.com and delete all your certificates and provisioning profiles. Generate new certificates with your one true key.

请确保您的捆绑包标识符对于您的应用程序是正确的-您甚至可能希望生成新的应用程序ID.

Make sure your bundle identifiers are correct for your apps - you may even want to generate new App IDs.

完成所有操作后，您便会生成配置文件.有了有效的证书，应用程序ID和密钥，您应该没有任何困难.供应配置文件确实很重要，但它取决于所有其他配置文件.对我来说，最大的考验是当我将其拖动到Xcode Organizer库中时-如果有一个目标，然后让我使用与配置文件匹配的证书签署构建，则我非常有信心.

Once that's all done you generate the provisioning profile. With a valid certificate, app ID and keys you should have no difficulties. The provisioning profile is the bit that really matters but it depends on all the rest. The big test for me is when I drag it into the Xcode Organizer library - if a target then lets me sign a build with a certificate matched by a provisioning profile, I'm pretty confident.

这篇关于如何准备要提交给应用商店的应用?我* KEEP *收到代码签名错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！