Skip to main content

Preparing mobile apps for signing

Suggest edit
Updated on March 3, 2022

Before you generate an installation package for your Android or iOS app, you must prepare the app for signing by creating a certificate set. With a complete certificate set, you can build the app and ensure that users can install the app on their devices.

In Pega Platform, you create Android and iOS certificate sets that consist of keys and certificates that sign the app when you generate the installation package.

When you sign your Android or iOS app, you provide a digital authentication for the app and guarantee that the app and its updates come from a legitimate source. If you do not sign your app, testing or running the app on mobile devices is not possible.

What to do next: Discover more about certificate sets in the following topics:
  • Configuring mobile build server settings

    Ensure that you properly configure your build server settings before you generate an Android or iOS application package for your mobile app. Incorrect or missing build server credentials disable the option to build an app in the mobile channel.

  • Default security settings for mobile apps

    Pega Platform includes default security mechanisms that help you generate secure mobile apps.

  • Building mobile apps

    Convert your application into a mobile app that users can install on their mobile devices. You can generate both Android and iOS apps, which helps you meet the needs of a wide array of mobile users.

  • Understanding certificate sets for Android

    A certificate set stores all the keys and certificates that are necessary to build, run, and distribute Android apps.

  • Understanding certificate sets for iOS

    A certificate set stores all the keys and certificates that are necessary to build, run, and distribute iOS apps.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us