Sample Mobile Build Project

In this document, a sample project BOA has been registered to help you understand the steps involved in registering a project on slave 2.

The files used for the BOA project are:

The CM team must ensure that the following files are kept ready by the implementation teams before registering the project. For more information on these files, refer Project Registration.

iOS Platform:

  1. BOA's Code signing certificate for iOS platform - iPhone Distribution: INTELLECT DESIGN ARENA LIMITED
  2. BOA's Provisioning profile for iOS platform - BOA_release.mobileprovision

Android Platform:

  1. Keystore - BOA_Android.keystore
  2. JSON properties file - BOA_keystoreprop.json


For registering the project, perform the following steps:

For details on the properties listed in the registration process, refer the About Properties Files.


  1. In the Terminal on slave 2, execute ant register in the CTMobileHybrid directory. Press return.

    The registration begins. The Terminal prompts you to enter the project name.

    If you closed the Terminal after setting up the template, follow these steps:

    1. Open the Terminal.
    2. Type pwd and press return. The directory changes to the folder previously accessed, which per the example in this document is: /Users/admin/Documents/MobileTemplate/CTMobileHybrid.
    3. Execute ant register.





  2. Enter the Project Name. Press return.

    The Terminal prompts you to enter the project identifier.



  3. Enter the Project Identifier. This is the unique ID provided to the app (for example, com.intellect.BOA). Press return.

    The Terminal prompts you to enter the required platforms for the project.



  4. Enter the mobile platforms to be included for the app. You can add multiple platforms by separating the values with a comma. Press return.

    The Terminal prompts you to enter the target framework.

    • The available platforms are iOS and Android.
    • You must enter the platform names as they appear in the screenshot. Otherwise, the Terminal will throw an error.




  5. Enter the target framework for the app. Press return.

    The Terminal prompts you to enter the project distributor name.

    • The available frameworks are JQM (jQuery Mobile) and JQTBS (Bootstrap). However, currently the Centralized Mobile Build only uses JQM for mobile apps.
    • You must enter the framework names as they appear in the screenshot. Otherwise, the Terminal will throw an error.




  6. Ensure that the project identity for iOS (distributor name) is present in the Mac system's keychain. To locate the distributor name, enter Keychain Access in the Spotlight Search bar on the Mac desktop browser. Navigate to Certificates. Select the distribution certificate created for this project. Double-click on the certificate. The distributor certificate opens.

    Shortcut to open the Spotlight Search bar is Command key + spacebar.





  7. Copy the Distributor name from the certificate.

    You must copy the name from the certificate as shown in the following image.



    If you are registering the project for a development build, you need to copy the developer name as shown in the following image:

  8. Paste the Distributor name. Press return.




  9. After you enter the distributor name, the Terminal displays the message 'Please verify if the signing identity you entered exists in the following result.' Check if the distributor name is available in the result. Press return.

    The Terminal specifies a path where you need to copy the provisioning profile.



  10. Copy the provisioning profile to the path indicated in the Terminal. Enter the Provisioning profile with the extension. Press return.



    • Each app requires a unique provisioning profile even if the app is being registered by the same company.
    • You must enter the provisioning profile with the file extension. Otherwise, the Terminal will throw an error. For example, if you fail to enter the extension, you may encounter the following error:


    The iOS platform is created for the project and the registration for the Android platform begins.




  11. Copy the keystore file to the path indicated in the Terminal. Enter the keystore name with the extension. Press return.

    • You must enter the keystore name with the file extension. Otherwise, the Terminal will throw an error.
    • The same keystore file can be used for registering multiple Android apps of a particular company.



    The Terminal prompts you to create a JSON file and copy it to the indicated path.


  12. Copy the JSON file to the indicated path. Enter the keystore properties JSON with the extension. Press return.

    • You must enter the keystore properties JSON with the file extension. Otherwise, the Terminal will throw an error.
    • The same keystore properties JSON file can be used for registering multiple Android apps of a particular company.



    The property file is validated and the Android platform is created.



    If you have followed the steps correctly, the message 'You have successfully registered to use CT Centralized Build' displays.



  13. Close the Terminal.


Refer Additional Steps for iOS Platform for more details.