How would I go about creating an Xcode project for iOS that can be compiled by anyone?
What I am trying to do, is to write a simple app and send the whole thing (just archive the whole project folder) to a friend so that he can compile it and test it on his own device.
Both of us are registered separately as individual iOS developers; we can both download example projects and run them successfully; and I can run my app on my iPad. However, when I send the archive to my colleague, he can’t test it (he says it builds but does not attempt to install or run on the device, only complaining “valid signing identity not found”).
Clearly I am not understanding something in the process about how development profiles work. There must surely be some way to produce a project that can be compiled by anyone, and doesn’t require my profile to be on the machine, or example projects wouldn’t be able to compile? (And why should a project in source-only form even need a profile attached to it?)
Am I understanding correctly that 1) I’ve somehow bundled my personal developer information into the source-only project, and this is stopping it from being built by another unconnected developer, and 2) that if so, it is actually possible to share projects in this way? How would I go about separating the project from the profile?
I am dimly aware that this is also the “wrong” way to share projects: I am open to suggestions for changing that too, but still want to understand what I’m doing wrong, and where I’ve missed something that must be obvious in the provisioning process.
You’d provide the project file, resources, and code just as you would for projects on other platforms. Don’t provide your developer provision profile or keys — each person who wants to build the project will have to supply those on his or her own.
He’ll need to supply his own developer profile and key.
Because the iOS devices won’t execute code that’s not properly signed.
Nothing to do here — your provision profile and keys are stored in your keychain, not in the project itself.
It’s really not “wrong,” but it’s not the easiest way to go if you’re going to be sharing frequently. There are services out there that provide cheap or free version control for small groups or open source projects, and sharing that way is a lot easier than mailing copies of the project back and forth.