Automatic packaging and signing services

After you upload an app to UFT Mobile, the server automatically attempts to package the app. This provides users with the option of selecting either a packaged app or the original version when running a test. To enable UFT Mobile to automatically sign and package apps, the administrator needs to set up the packaging and signing services.

In this topic:

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 to automatically re-sign apps. This is done by configuring the packager properties file.

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

Configure app signing services for iOS apps (on-premises)

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

You can set up the packaging and signing service to automatically sign and package iOS apps when they are uploaded to UFTM. The packaging service can also be used for signing the Agents. For details, see Signing services for iOS apps (on-premises).

Back to top

Configure app signing services for Android apps requiring a private key (on-premises)

This section is relevant only for on-premises deployments of UFT Mobile. In general, automatic packaging of apps after upload to UFT Mobile requires no additional action.

If your app uses services that require a private key, such as Google Maps or the authentication service, you need to sign your app using your own private key. To enable UFT Mobile to automatically sign your app with your own private key during the packaging process, you need to first set up the app packager for signing Android apps.

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 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 you will use 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.
   
   

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 and packaging for UFT Mobile SaaS

The automatic signing and packaging service is hosted.

iOS

Open a service request for a dedicated signing/packaging service using your Apple certificate and provisioning profile. When this service is set up, the Agent apps, as well as any app uploaded to UFT Mobile, will be signed automatically with your Apple certificate and provisioning profile.

Alternatively, if you choose not to set up automatic packaging, 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. When using manual packaging and signing, set the Autopacking toggle to OFF.

Define packaging settings in UFT Mobile

You can set up UFT Mobile so that when a user uploads an app, UFT Mobile automatically packages the app with record and replay libraries.

1. In UFT Mobile, click Administration and select the SETTINGS tab. For multiple shared space environments, see Global settings for iOS Packager settings.
   
2. In the packaging service sections (for Android or iOS), set the IP address and port of the machine that will be used for repackaging the app. Set the protocol type to HTTP or HTTPS, depending on whether the connection is secure.
Android: 
• The packaging service machine is set to localhost by default.
• You can enable packaged apps to trust Android User Certificates. This is required when recording a script for load testing using the VuGen MITM protocol.
iOS 
• Use the Add Service button to add other packaging services in addition to the primary one. For these additional services, you also indicate the workspace that will use this service. Use the Remove button to remove packaging services that you added. The primary service cannot be removed.
• If you enable SSL for the connection to the app packager, you can use the self-signed certificate or use a certificate issued by a Certificate Authority (CA). When using a self-signed certificate, you can either import it to the UFT Mobile server or disable the iOS app packager certificate validation setting.

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:

• Package an iOS app manually with the packager service
• Package an Android app manually
• Upgrade packaged apps (on-premises)