Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring mobile build server settings

Updated on November 9, 2021

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.

Before you begin:
  • If you do not have Mobile Build Service account credentials, ask your Pega client representative to submit a ticket in My Support Portal and request these credentials for you.
    Note: Mobile Build Service account credentials consist of an account name and an API key.
  • Ensure that you can access Admin Studio in your Pega Platform instance.

    For more information, see Admin Studio overview.

  1. In the navigation pane of Admin Studio, click MobileSettings.
  2. In the Mobile app build server section, enter the Mobile Build Service account name and API key.
  3. Optional: To disable the authentication requirement when a user downloads your app, clear the Require login for mobile app download check box.
  4. Confirm your changes by clicking Save.
Result: When you save the changes to the mobile build server configuration in Admin Studio, Pega Platform creates the following dynamic system settings:
  • pega/mobilebuild/server/account
  • pega/mobilebuild/server/encrypted_key
These dynamic system settings are responsible for correct authentication in the mobile build server.
For example:
Example of a mobile build server configuration
Sample mobile build server configuration settings in Admin Studio.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us