Automatic signing services

To enable users to sign apps when uploading them to UFT Mobile, the administrator needs to set up the signing services.

About app signing services

Whenever an app is repackaged with UFT Mobile record and replay libraries, the app needs to be re-signed. By default, Android apps are signed with a debug certificate, and no additional action is required by the administrator. For iOS apps, or for Android apps that use services requiring a private key such as Google Maps or the Authentication service, the administrator needs to set up UFT Mobile for automatic signing.

You can also package and sign apps manually and then upload them to UFT Mobile. For details, see Package an Android app manually or Package an iOS app manually with the packager service.

Back to top

Signing service for iOS apps

You set up the iOS signing service so that iOS apps can be signed when they are uploaded to UFTM. The signing service is also used for signing the Agents. For details, see iOS signing service.

Back to top

Signing service for Android apps requiring a private key (on-premises)

This section is relevant only for on-premises deployments of UFT Mobile.

In general, packaging of Android apps on upload to UFT Mobile requires no additional action. To view the settings configured for the Android packager, click Administration > Settings tab and select Android packaging service. For more details, see Administration settings.

By default, UFT Mobile signs your app with a debug certificate. If your app uses services that require a private key, for example Google Maps or the Authentication service, you need to sign your app with your own private key during the packaging process. To enable UFT Mobile to sign using a private key, you need configure the app packager to use your signing details.

To configure UFT Mobile to automatically sign your app with your own certificate:

  1. Open the packager properties file on the UFT Mobile Server machine:
    Linux: <Path to your server installation folder>/server/conf/packager.properties
    Windows: <Path to your server installation folder>\server\conf\packager.properties
  2. Enter the following information:
    • ANDROID_KEYSTORE_PATH = The path to your key store, which is a binary file containing your set of private keys.
    • ANDROID_KEY_PASSWORD = The password for the private key that will be used to sign the app.
    • ANDROID_STORE_PASSWORD = The password for the key store.
    • ANDROID_ALIAS_NAME =The name used to identify the private key entry in the key store.
  3. Note:  All four values are required. If any of the values is left empty, the app packaging process will fail.

Back to top

Automatic signing for UFT Mobile SaaS

To set up automatic signing services for iOS and Android when using UFT Mobile SaaS:

iOS

Configure the embedded signing service. For details, see iOS signing service. When this service is set up, the Agents and all other apps uploaded to UFT Mobile can be signed with your Apple certificate and provisioning profile.

Alternatively, if you choose not to set up automatic signing, you can manually sign the Agents and your apps using the iOS Enabler. For details, see Package an iOS app manually with the iOS Enabler.

Android

By default, UFT Mobile signs your app with a debug certificate. If your app uses services that require a private key, for example Google Maps or the Authentication service, open a service request for a dedicated signing service to sign your app with your own private key. Alternatively, you can package the app manually and then upload it. For details, see Package an Android app manually.

Back to top

Troubleshooting the app packager

There may be times when the packaging process does not succeed. When UFT Mobile is unable to create a packaged version of the app, a notification is displayed. Packaging is not essential for testing, however, there are certain test cases that require the app to be packaged. For details, see When to use a packaged app.

Packaging may not succeed for the following reasons:

See also: