Actually in my experience I need only one certificate, but I need different provisioning profiles.
When you first sign up, you go thru the painful certificate creation process. Its like good for a year, but you can renew it, I think.
Then FOR EACH APP
You create a unique App ID bundle. That App ID is a combination of a 10 Alpah digit code Apple Generates (though I can’t seem to make new ones any more) and a string, which is your reverse domain name with a subdomain for each app that DOES NOT share a keychain (multiple apps using one set of passwords).
Your AppID will look something like:
ABC123ZYZ5.com.omnigeekmedia.omniblaster
where the ABC123ZYX5 is the ID generated by Apple. com.omnigeekmedia is the reverse of my domain name: omnigeekmedia.com and the .omniblaster is a unique string to make your app unique in your name space. In my case, when I release a new app, I setup a website for it, that has the URL omniblaster.omnigeekmedia.com just to keep things consistent.
Now once you have a unique AppID for your app, you need 1 to 3 “Provisioning Profiles”:
Development
Ad Hoc
Distribution
You need a Development one if you’re going to run a tool like “Instruments” on it to look for memory leaks. There are a few other uses for a Development profile.
If you want to give your app to people to test, or if you want to do an distribution within your company, you can install on up to 100 devices. If you use a service like testflightapp, you will use this provisioning profile. I typically use it to build my device test builds. You cannot test on a device without one of the two above profiles.
Finally you will need a distribution profile for releasing to Apple. This profile WILL NOT install directly to a device but must be downloaded from iTunes.
You should have a unique Provisioning Profile for EACH app. [import]uid: 19626 topic_id: 18671 reply_id: 71776[/import]