I am really confused with ios provisioning profile. Can I use one Development Provisioning Profile for multiple apps? Same question for Distribution Provisioning Profile.
thanks for your help.
Yes, you can use the same certificates for multiple apps.
It may seem complicated, but once you look at it, it's not so bad. Here's the breakdown:
The development provisioning profile gives you the opportunity to test apps you create (any) until you try to push it to Apple. When you do that, the distribution profile comes into play. Essentially, it connects any apps you produce with your App Store storefront.
Related
I recently uploaded my first iPhone app to the App Store, and i'm thinking of creating a new app. I am wondering what new things I will need to create for it to be submitted. Examples: Bundle ID's, Certificates, or Provisioning Profiles, etc. Thanks!
You'll need everything you needed for the first app, except that your distribution certificate is a personal identity and lives in your keychain and at the Portal, so you only need one of those (until it expires, when you'll need to make a new one).
It might help if I make you a little chart here.
YOU: There is only one of you, so you only need one development certificate and one distribution certificate.
APP: Each app has its own bundle id and you'll need to tell that Portal what that is if you want to submit it to the store or hand it out in an ad hoc distribution.
PROFILE: A profile unites YOU and one APP. Thus it is unique to that APP and you'll need a new one for every APP you want to distribute. -- EXCEPTION: For convenience, Apple now allows you to develop many kinds of app on a device using a single team development profile where the APP is effectively a wild card. This was not always the case though; it used to be that you needed a new development profile for every app too, just as you need a new distribution profile for every app. And for apps with special needs you may still need a development profile just for that app.
I'm stuck with this damn "Application failed codesign verification" warning that I simply can't solve... I'm about to submit my app to Apple. :(
Having a look to my provisioning profiles made me realize that the status of my development profile is "Active, managed by Xcode" whereas my distribution profile is only "Active". It may be the reason of this problem because anything else seems to be OK. So what is wrong here ?
Thanks a lot for your advices.
Having a look to my provisioning profiles made me realize that the
status of my development profile is "Active, managed by Xcode" whereas
my distribution profile is only "Active".
The team development profile includes certificates for all the developers on your team and device ID's for all your devices. Since only one person is authorized to distribute applications for any given account, and since there are no device ID's associated with the distribution provision, there's no need to have Xcode or the provisioning portal manage your distribution provision -- there'd be very little to manage.
It may be the reason of this problem because anything else seems to be
OK. So what is wrong here?
No, difference in the description of your development and distribution profiles isn't the problem. The problem is that the codesign utility was, for some reason, unable to sign your application. There are several things that can prevent your app from being signed, such as:
Wrong distribution profile selected in your project's build settings.
App ID in distribution profile doesn't match that of the app you're trying to sign.
Problem with distribution profile, e.g. an expired certificate.
There are also a great many questions right here on SO pertaining to signing your app for distribution. It doesn't make sense to rehash all those answers here, especially without more information about what you've already checked or at least seeing the specific error. Take a look at some of those questions first and see if something rings a bell. Otherwise, take a look at the Troubleshooting section of the Tools Workflow Guide.
My app is currently well-developed but not released on App store. 40 volunteers are willing to test my app. I want to let them test my app by Over The Air (OTA) Ad Hoc distribtuion.
However, since i need their UDIDs to set their iPhones as test devices on iOS provisioning portal, test users might not want to give such private information.
Besides, does provisioning file contain all the UDIDs of test users?
I am afraid of that all the UDIDs would be known if someone opens the provisioning file.
Are there experienced developers who already successfully persuade test users to give their UDIDs for Ad Hoc distribution?
Since a company will contact test users, they said it's really hard to ask test users' UDIDs. Is it any second solution?
I would agree that it is awkward to ask people for their UDID.
There is a free app that will let them automatically send their UDID to you. I find it's not only easier to persuade test users to use it, it also makes the process easier for them.
https://itunes.apple.com/us/app/ad-hoc-helper/id285691333
After recently joining the Apple Developer Program I am trying to understand the best approach when creating provisioning profiles.
The fundamental aspect that is not clear is the relationship between the AppID in the provisioning profile and the actual application.
For example, I created the profile
MyApp1Profile
and successfully installed it in XCode.
However, this profile works in any of my XCode projects/apps and allows me to run the apps on my device.
Is MyApp1Profile supposed to be associated w/ MyApp1 in some way?
Why does this profile work w/ other apps?
Do you set up different profiles for the same app, e.g., testing and release?
If I am going to be developing multiple apps in different projects does anyone have links to potential best practices on creating profiles?
I'd like to start doing limited beta testing of an iOS app. I know how to do regular ad-hoc distribution of my existing app, but I've had one of my potential beta users tell me that when they test other apps, they end up having a separate app installed alongside the production one. But I don't know what the other developers are doing to create this.
Do I need to burn up a fresh app ID registered with Apple (and app name that will never be real) to accomplish this for my beta users?
If so, is there a reasonable way to manage this within a single Xcode project?
Thanks from anyone with experience here. I know I'm toying with the line of "programming question", but this is certainly the community with the right expertise. Thanks! :)
Just set a different bundle identifier in your Info.plist.
Personally, I create three configurations in my project (Debug, Ad Hoc, App Store) and then define a user-defined build setting for each config (BUNDLE_IDENTIFIER) in which I set the different bundle IDs.
In my Info.plist, I can then set the bundle ID as ${BUNDLE_IDENTIFIER}.