Skip to main content

Types of provisioning profiles:-


There are four types of provisioning profiles. They are Development, App Store, Ad-Hoc, and Enterprise.  They are used for different purposes and should be only used for those purposes.


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:-
  1. You want to test your app the use - Development Provisioning Profile.
  2. Test multiple users without interaction with APP store then use - Ad-hoc                      distribution provisioning profile.    
  3. Multiple user's interactions with app store then use - App store distribution provisioning profiles.
  4. 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

Popular posts from this blog

Collect console logs for iOS devices

Mostly I work in a windows environment and it is necessary to get console logs for iOS devices to find out the root cause of the issue. We can get iOS app crash log from this path ( C:\Users\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\DSS-Iphone 6 ) in windows machine using iTunes. But we need an entire app log to understand what goes wrong in the application. And after some research, I found iTools which allow you to manage iOS devices and also show entire device logs. This tool helps me to do my testing. As per my understanding, this tool will not run without iTunes. iTools was also affected by the latest iTunes update. Now I have found some other tool called 'iOSLogInfo'. Download and run iOSLogInfo to get console log for iOS devices in windows. Requirements:- iOSLogInfo ( Download link - https://www.blackberry.com/blackberrytraining/web/KB_Resources/KB36986_iOSLogInfo_4.3.4.zip    ) iTunes for windows Steps:- Download and save iOSLogInfo z
5 comments
Read more

Android Application Automation Testing using MonkeyTalk IDE Professional

Steps to install and run the MonkeyTalk scripts 1. Download Monkey Talk IDE and AspectJ from given link:     https://www.cloudmonkeymobile.com/monkeytalk     Download Eclipse 4.3.1 or 4.3.2 (for Windows) from given link and copy in    your C Drive.     https://www.eclipse.org/downloads/packages/eclipse-standard-432/keplersr2 2. Launch Eclipse and install AspectJ for respective eclipse version.      aspectj - http://download.eclipse.org/tools/ajdt/37/update 3. Now get the app source code from your developer which you want to test and import it in eclipse. 4. Right Click on your project >> Configure >> Convert to AspectJ project.      5. Check you have "libs" folder or not.If you have then OK or else create a new "libs" folder. 6. Now open Monkey Talk\monkeytalk\agents\android\ monkeytalk-agent-2.0.5.jar folder that we downloaded in step 1. Drag & copy the agent.jar file in libs folder. 7. Now Right Click on newly c
Post a Comment
Read more

AI in Software Testing

AI Testing In the span of only a few months, AI has reshaped the landscape of almost every industry around the world in both positive and negative ways. Indeed, there is still a lot of room for improvement in this groundbreaking technology, but if businesses don’t embrace it, they’re sure to be left behind. In the QA industry, “AI testing” will become the norm in the next few years, bringing incredible advancements in the way we think and do software testing. In this article, we’ll explore the concept of AI testing in-depth, see how AI can optimize testing, and share the pioneering AI testing tools that you can leverage to transform your QA workflows. What is AI? Before diving into the concept of AI testing, we must first have a common understanding of Artificial Intelligence (AI). AI has become a buzzword recently after the introduction of ChatGPT – a revolutionizing chatbot. So, what is AI? AI can be defined as the simulation of human intelligence via machines that are programmed to
Post a Comment
Read more