Provisioning - Step 1 : Create a Provisioning on Apple Site 


Introduction

This Tutorial is here to help you create an iOS Provisioning file on the Apple Developer Site.
It is important to note that Apple changes their requirements without warning.
We do our best but the Apple site might change without us knowing. 
 

If you try to install an app on your phone and see this kind of message:

That means your device is likely not in your provisioning.
It is time to install, update or add that device into your Provisioning file.

Here are the steps you're going to be doing to create 2 provisioning files that will be uploaded to the EachScape builder.

1. Create an "Identifier" in the Apple Developer console. This is the unique identifier for your app. This file should never be deleted. If you remove this from the Apple Developer console you won't be able to update your app in the future.
2. Add any devices in the Apple Developer console that you'll be using to test ad hoc builds (test builds) to your ad hoc provisioning
3. Create your ad hoc provisioning "Profile" in the Apple Developer console to upload to the EachScape builder. In this process you will point to your Certificate you created, your "Identifier" and any devices that you want to test your iOS builds on.

4. Create your Commercial provisioning "Profile" in the Apple Developer console. This will include your Certificate you created & your "Identifier". You will then download this file to upload to the EachScape builder.


Let's get started...


Step 1: Create an Identifier

Step 1: Navigate to the Identifiers section of the Apple Developer site.

Click on "Identifier". This is the unique ID for your app that will live in the iOS store. Once this is used and uploaded to the iOS app store it can't be changed and needs to remain for future update. Never delete this Identifier once you use it or you will not be able to update your app in the store.



Now click on the "+" on the top right.



Nothing you define can change once it has been created, however none of it is displayed to end-users of the app.

Choose "App IDs" and then click "Continue"


Choose "App" and then click "Continue".




Choose an intuitive description.


The Bundle ID will be unique to the app that lives in the app store.


For example, if your company's web site is at www.example.com, then the Bundle ID can be something "com.example.appname".

If you want to create a default provisioning profile that can used for many AdHoc builds:
Choose Wildcard App ID instead.

 The Bundle ID 
should be something "com.example.*" as it must always end with an asterisk.
 Wildcard App IDs cannot be used for commercial builds but they're a great way to build many test apps.

 
Once done click Continue.



On the next screen review your information and then click on "Register".


Your "Identifier" is now complete. You'll use this along with your certificate to create the Provisioning files to upload to the EachScape Builder.



 Step 2: add devices that you want to use for ad hoc builds


You'll need to get the UDID of any iOS phone or tablet device you want to use for testing your ad hoc builds.

Here is how to get the UDID of your device: Finding your iPhone, iPod touch or iPad unique ID (UDID) 

In the main screen for Certificates Identifiers & Profiles click on "Devices" then click on the "+" sign.


Under "Platform" choose "iOS, tvOS, Watch OS"

Under "Device Name" enter an intuitive name for your device.

Under "Device ID (UDID) enter your UDID from your device that you got in the previous step.

Click on "Continue"



Do these steps for any iOS devices that you want to add to your ad hoc Provision Profile.


We can now continue to the next step.



Step 3: Create the ad hoc and Commercial Provisioning File "Profiles"


We now need to create 2 profiles to upload to the EachScape Builder. Your "ad hoc" "Profile" will be for building and testing in devices or the Xcode simulator. We'll also create a "commercial" "Profile" in order to create the app build that will be uploaded to the app store.


Let's create the "ad hoc" "Profile" first.


Click on "Profiles".




Now click on the "+" on the top right.



Now choose the type of Distribution that you want.A single account will not see all of these choices concurrently.
  • App Store is used for Commercial Distribution in the iTunes store.
  • Ad Hoc distribution is for sharing apps to a limited number of devices before the app is in the store


Under "Distribution" choose "Ad Hoc" the click "Continue".



No choose your "App ID" that your created in your last step the click "Continue"




Now choose the Certificate that you created and uploaded to the EachScape builder.
Then Click on "Continue".


This next view, if you have chosen Ad Hoc Distribution you'll be allowed to add any iOS devices that you have added in the previous steps. If you use any iOS device iPhone or Tablet to install and test your builds will need to be registered in the "Devices" section of your developer account.

Once you've selected your devices to add to your ad hoc provisioning then click on "Continue"


 

Generally the easiest thing to do is to click "Select All" unless you want to restrict the app to a subset of the devices listed.



We strongly encourage you to include the word "ad hoc" or some other intuitive name to keep track of what the profile is in the name of the file when you are creating a certificate to install a test your app builds. Then click on "Generate"


Now click on "Download" to get the "ad hoc" provisioning file you're going to upload to the EachScape builder




Now let's create our "Commercial" provisioning in the App Developer Console.


Click on "Profiles" then click on the "+" sign.


Under "Distribution" choose "App Store" then click on "Continue"




Choose the "App ID" for your App. Then click on "Continue"


Choose the "Certificate" that you created and uploaded to the EachScape builder in previous steps. Then click "Continue".




When you fill out "Provisioning Profile Name" we strongly encourage you to include the word "Commercial" or some other intuitive name to keep track of what the profile is in the name of the file when you are creating a certificate to install a test your app builds. Then click on "Generate".




You can now click "Download" to get your Provisioning file to upload to the EachScape Builder.



 

Provisioning - Step 2 : Upload Provisioning into EachScape