XCode 5.0.2 will not sign my app

Everything has to be signed with the same signature. Xcode5 can be picky about identiries. If you choose the automatic "Mac Developer", it sometimes (usually) doesn't pick the correct one.

Unfortunately, the only way around this is to submit a lot of apps. If you only submit an app every six months, you either forget how to do it or Xcode changes everything and you have to re-learn. There is no magic bullet. It is just really confusing.

In many ways, the original process was better. It was really difficult, but it was so difficult that Apple had to provide step-by-step instructions or else no one could figure it out. Now you need Xcode integration and hopefully it doesn't scramble and/or dup your certificates. You need provisioning profiles, or not. You need a developer certificate, or installer, or distributor, or 3rd party developer/distributor - whichever is apprpriate. Xcode will conveniently re-set all those values each time you open the project. Everything has to be signed, but not the way you used to do it. Xcode can conviently do it for you, as long as everything is in Xcode and is exactly set up in the specific way Xode needs so that Xcode can conveniently do it for you.

Stele wrote:

Can someone make sense of this?

On second though. Perhaps not. 🙂

It is difficult to tell, because Xcode does reset everything, but your Code Signing Identity should be set to one of your "Identities in Keychain" - "Mac Developer: Whoever you are DSD799ss".

Anything in the bundle needs to be signed with the same identity.

Unless you are doing something that needs a Provisioning Profile, leave that "None".

.

Stele wrote:

What about it doesn't "storeagent" like?

The --deep part. You can't do that anymore in Xcode5. You have to add external frameworks the "correct" way or manually code sign them in a separate build phase.

Stele wrote:

Hmm - could you elaborate on the "correct" way to add external frameworks?

It is a bit of a long story. Apple wants everyone to use workspaces. You add all of your projects to a workspace and Xcode will magically figure it all out. I still don't understand that in detail and I don't like to jump into things when I'm not confident. I'm just statically linking anything external. It won't be until next year until I get to the project where I need to worry about this.

I do have a Copy Frameworks phase in my Build Phases, but they are not signed.

That is what I have been doing in the past. You have to add a build phase to sign them. On the project where I have been playing around with this, I already had a separate buidl phrase to run install_name_tool to fix up the dynamic library paths. The "workspace magic" I mentioned above is supposed to eliminate both of these steps.

If I were to manually sign them, which codesign signature should I use?

The same one you sign the rest of your code with.

The only thing I have different is Developer ID Application: yada yada yada

However, all of mine are in my individual name. I don't have a company account (any more). Why would you have all of those certificates in a company name and one in your own name?

Maybe look at those certificates on the web site and double check. Then download and install them manually. I don't really trust Xcode with those things anyway after it created a duplicate Developer ID which cannot ever be deleted.