Development provisioning profiles:-
Development Provisioning
profiles are used only while developing an application. Developers use these
profiles so that they can actively debug their code, and test on different
devices. They are not designed to be used for mass distribution.
Only use these profiles for development and debug builds. These are
assigned to individual developers and are used to identify them. Also,
Development Provisioning Profiles can only be created with Development Signing
Certificates (this is important to remember).
Ad hoc distribution provisioning profiles:-
Ad hoc testing is when you have completed
development and want to distribute your app to multiple users for testing (your
second question). Just create a distribution profile for ad hoc testing and
select all the device ids for which the profile is valid. In that case, you
will only need to send the .app file and .mobileprovision file to each user
testing your app. Details Description - If you'd like to install your software
on several devices without using the App Store, you'll have to create an Ad Hoc
distribution profile with the device ID numbers, and install that profile as
well as the software, on all of the devices. Ad-hoc profiles are similar to
development profiles. There is one key difference between Ad-hoc profile and
development that make their intended usage differ. The key difference is when
you want to test out different entitlement services, such as push
notifications.
App store distribution provisioning profiles:-
App Store Provisioning
Profiles are to be used after your app has passed QA and is fully tested
to the best of your ability. This is the profile you want to use when you
submit your application to the Apple App Store. In fact, Apple will not
let you submit your app if it is not built with an App Store Provisioning
Profile. There are some key differences here. One major different
is that a list of UDIDs is not required for an App Store Provisioning
Profile. This is okay because when Apple approves your app to be
distributed through the App Store, they re-sign your application using their
own signing certificate and profile. This is the magic key that allows
your app to run on all iOS devices without limitation. Though the App
Store Provisioning is necessary because this is Apple’s verification that the
submission has come from you or your company and not someone else pretending to
be you.
Enterprise provisioning profiles:-
Enterprise Provisioning
Profiles are very similar to Ad-Hoc Provisioning profiles, but with some key
differences. The first difference is that in order to obtain an
Enterprise Provisioning Profile, your company must join the "Apple iOS
developer enterprise program" ($299 USD / year). This is a
separate program than the “iOS Developer Program” that you may already be
registered to. Joining the Enterprise Developer Program is strict, and a
key requirement is that your company must have a valid D-N-U-S number
(It is a unique nine-digit number that identifies business entities and
organization status on a location-specific basis. Assigned and maintained by
DUN & Bradstreet (D&B), the D-N-U-S number is widely used as a standard
business identifier). And they are only issued to legal business
entities. If your business does not have a valid D-U-N-S number, then
Apple will not allow you to join the Enterprise Developer Program.
Note:-
- You want to test your app the use - Development Provisioning Profile.
- Test multiple users without interaction with APP store then use - Ad-hoc distribution provisioning profile.
- Multiple user's interactions with app store then use - App store distribution provisioning profiles.
- If you want to deploy an app for internal use only amongst employees, then use enterprise provisioning profile. You need an enterprise developer account and require your own server to host the apps.
Comments
Post a Comment