Project Registration for Mobile Build

Owned by Ravikumar Babu CTOO (Unlicensed)
Last updated: Jan 17, 2019 by Vaishnavi Sridhar (Unlicensed)
  • The steps listed in this section must be performed by the CM team. The implementation teams must sit with the CM team to provide inputs that are required for the project registration.
  • As the scope of the document is to provide steps to package apps for a release, only information pertaining to that have been provided in this section.


After the template is setup, the next step for the CM team is to register the project. 

Prerequisite: The template for the app must be setup in the template folder. The implementation team needs to provide the following information to the CM team for the iOS and Android platforms:

iOS

  1. Code signing certificate: This certificate allows developers to digitally sign their software before distribution over the Web. End users downloading the digitally signed program can be confident that the code has actually come from the developers and has not been modified since it was signed. For more information on this refer https://developer.apple.com.

  2. Provisioning profile: The provisioning profile contains a set of iPhone development certificates, unique device identifiers, and an App ID. It uniquely ties developers and devices to an authorized iPhone development team and enables a device to be used for testing. For more information on this refer https://developer.apple.com.

Android

  1. Keystore: The Android market requires the developer to sign all apps that are published with a certificate, using a public or private key mechanism (the certificate is signed with the developers' private key). This provides a layer of security that prevents, among other things, remote attackers from pushing malicious updates to the application to market (all updates must be signed with the same key).

  2. JSON properties file: This file stores the keystore properties such as:
    1. keystore: Path to a binary file that can hold a set of keys.
    2. StorePassword: Password to the keystore.
    3. alias: The ID specifying the private key used for signing.
    4. password: Password for the private key specified.
    5. keystoreType (optional): This property can be ignored.

      The following screenshot is an example of the properties required for the keystore:


      For more information on keystore and its properties, refer https://developer.android.com/studio/publish/app-signing.html.


Refer the following pages: