Share this page

# Package an Android app manually

You can manually package your app from the command line using the Android Enabler tool.

In this topic:

## Prerequisites

1. The packaging process should be run on a machine that meets the following requirements:
   - The JAVA_HOME environment variable is defined.
   - 1.5 GB free RAM (Recommended)

2. Copy the following to the testing tool machine:

   - AndroidTools folder. You can find this folder in the server folder on the OpenText Functional Testing Lab server machine.
   - Your app (.apk file)

Back to top

## Sign the app with your own Android certificate

To sign the app with your own Android certificate, run the Android Enabler on your app from the command line:

Windows

`<Path to AndroidTools folder>\DLAndroidEnabler.bat –keystore <Android key store path> –alias <Android alias name> –storepass <Android store password> -keypass <Android key password> –hybrid –native <path to your application>`

Linux

`<Path to AndroidTools folder>/DLAndroidEnabler.sh –keystore <Android key store path> –alias <Android alias name> –storepass <Android store password> -keypass <Android key password> –hybrid –native <path to your application>`

Parameter | Details
--- | ---
–keystore | The path to keystore file containing your set of private keys.
–alias | The name used to identify the private key entry in the key store.
-storepass | The password for the key store.
-keypass | The password for the private key used to sign your apps.
-hybrid | Enable packaging of hybrid app.
-native | Enable packaging of native app.
-removeSecuredLayout | Remove the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations.

The packaging process consists of a number of steps. Wait for the steps to be completed successfully.
The result is an APK file signed with your android certificate. For example, running the above command on my-android-app.apk generates the file: my-android-app.apk.signed.apk in the same folder as the original APK file.

Upload the generated *.signed.apk file to OpenText Functional Testing Lab.

Back to top

## Sign the app with a debug Android certificate

To sign the app with a debug Android certificate, run the Android Enabler on your app from the command line:

Windows

`<Path to AndroidTools folder>\DLAndroidEnabler.bat –native –hybrid –signdebug <path to your application>`

Linux

`<Path to AndroidTools folder>/DLAndroidEnabler.sh –native –hybrid –signdebug <path to your application>`

Parameter | Details
--- | ---
–signdebug | Sign the app with the debug certificate.
-hybrid | Enable packaging of hybrid app.
-native | Enable packaging of native app.
-removeSecuredLayout | Remove the LayoutParams.FLAG_SECURE flag, when set, from any detected Window.setFlag() invocations.

The packaging process consists of a number of steps. Wait for the steps to be completed successfully.
The result is an APK file signed with the default debug certificate. For example, running the above command on my-android-app.apk generates the file my-android-app.apk.signed.debug.apk in the same folder as the original APK file.
Upload the generated *.signed.debug.apk file to OpenText Functional Testing Lab.

Back to top

See also:

- App packaging and signing services
- Package an iOS app manually with the packager service

https://admhelp.microfocus.com/Functional Testing Lab 8942
Tips to improve your search results... OpenText™ Functional Testing Lab for Mobile and Web Help Center OpenText™ Functional Testing Lab Help 25.2 All View Local Help Center View Online Help Center Version: