Code Signing for Build Automation

With the Telerik AppBuilder Plugin, you can automate only builds of application packages. You cannot create builds for the developer apps.

Sometimes, when you build an application package, you might need need to code sign it so that you can run it on device or distribute it to the app stores.

iOS Code Signing

When you build for iOS, you must code sign your application packages in order to run them on device or to distribute them to the App Store. In the Telerik AppBuilder Plugin, you need to provide the identifier of a provisioning profile and the alias for the matching certificate. If you want to build for the Apple Watch, you need to provide the identifier for the provisioning profile of the host app.

  1. Verify that your Account owner has configured the provisioning profile and certificate from their account. For more information about how to configure iOS code signing, see Code Signing of iOS Apps and Code Signing of Apple Watch Bundles.
  2. Verify that the Account owner has provided you with the alias for the certificate that you want to use. The following steps describe how to obtain a certificate alias in the in-browser client.
    1. In your browser, log in to the Telerik Platform.
    2. Open your app.
    3. In the top right corner, click the cogwheel icon and select Options.
    4. In the left-hand Options menu, select iOSCryptographic Identities.
    5. Write down the alias for the certificate that you want to use exactly as you see it, including the Team ID. For example: iPhone Developer John Doe (AB12CD34EF)
  3. To obtain the identifier for the provisioning profile, perform the following steps.
    1. In a text editor, open the .mobileprovision file for the provisioning profile.
      If you do not have it stored on your system, you can export it from AppBuilder.
    2. Locate the <key>UUID</key> line and copy the value for the key enclosed in the <string> tag below it.

Android Code Signing

When you build for Android, the Telerik AppBuilder Plugin does not require a code signing identity. If you do not configure a certificate in the UI of the Jenkins job, the Telerik AppBuilder Plugin uses a generic code signing identity. You will not be able to publish such builds in Google Play.

If you want to create self-signed or publishable builds of your Android apps, you need to provide your own self-signed certificate.

  1. Verify that your Account owner has configured the provisioning profile and certificate from their account. For more information about how to configure Android code signing, see Code Signing of Android Apps.
  2. Verify that the Account owner has provided you with the alias for the certificate that you want to use. The following steps describe how to obtain a certificate alias in the in-browser client.
    1. In your browser, log in to the Telerik Platform.
    2. Open your app.
    3. In the top right corner, click the cogwheel icon and select Options.
    4. In the left-hand Options menu, select AndroidCryptographic Identities.
    5. Write down the alias for the certificate that you want to use exactly as you see it. For example: John Doe

Windows Phone Code Signing

Currently, you cannot code sign Windows Phone packages. The Telerik AppBuilder Plugin always produces Telerik-signed application packages. To run the package on device, you need to install the Telerik Application Enrollment Token (AET) on the device first.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.