Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I remember before reading that if you used a wildcard provisioning id (eg net.nevan.*), you could have easier sharing of information between your apps. Now, many things require a provisioning id for each app to be unique (iAds, notifications, in-app purchase). Actually, looking at my apps on the app store, they are all using unique ids.
Is there still an advantage (other than convenience) to using a wildcard id for provisioning profiles?
The biggest plus is that if you don’t need unique provisioning profiles, you only need to make one once, and when it expires, you only need to refresh the one provisioning profile. If you’ve got 10 applications each with its own development and distribution provisioning profile, that’s 20 provisioning profiles you have to keep up with if you’re actively developing all 10 applications. Plus another profile each if you want to do any ad-hoc building for beta testers.