iOS Code signing Identity INSANITY!

[Bungler]

Resolved:
For anyone having this issue, when building an iPhone app, your app wont be codesigned by xcode unless you are using the DEVICE SDK not the Simulator. I'm apologize if this has been mentioned before, but it took 4 days of searching to get it signed.

The whole system, really, just needs to be greatly simplified.

 

[kalimba]

While it's obvious that many, many individuals have been bitten by "gotchas" (for which there appears to be little, if any, documentation to assist), the process went quite smoothly for me. I have to say that I was overly meticulous about going through the process step-by-step and did not have a single problem until I tried to deploy one of my projects onto my device. I got the 0xE800003A error and could not figure out what I had done wrong.

It took me a while to figure it out, but I'm nearly 100% sure that what ended up fixing it was doing a full "clean" of the project and rebuilding. I can only assume that, for whatever reason, changes to the .plist file and/or other project changes do not "dirty" the project such that subsequent builds incorporate those changes.

This is what worked for me. If you're stuck, as I was, hopefully it will work for you.

 

[firewood]

I suspect that Apple won't simplify the process much. It's become their qualifying exam.

If a developer can find, read and precisely follow on the order of 100 exacting steps required to correctly provision an app, without missing or messing up even one step, then their submitted apps are being built by a developer who is somewhat less likely to waste Apple review team's time with stupid bugs and flaws.

I've occasionally had to quit and restart XCode or the Keychain to get a provision working. I later found that those procedures are actually mentioned in Apple's documentation.