Android App Patching

App Live enables customers to use sensor instrumentation features, such as biometric authentication without getting their app resigned by BrowserStack, thus preventing authentication issues or invalid certificate issues during testing on BrowserStack devices.

Use App Patching for Android Apps

You must use the BrowserStack endpoint to patch your app, and then sign the app with your own certificate, thus resolving any issues that occur from app resigning.

App instrumentation involves:

a) Uploading an unsigned app (.apk) file to the BrowserStack endpoint and getting the instrumented app(. apk) file.

b) Signing the instrumented app with your certificates

c) Uploading the signed instrumented app to BrowserStack for using the sensor instrumentation features.

Get instrumented app

• Contact BrowserStack support to access an endpoint that you can use to get your app instrumented. You can save the instrumented app, new-path.apk, in a directory.

Sign Your Instrumented App

Prerequisites:

• android build-tools installed on your machine.
• Keystore or certificates from your developer.
• Access to Keystore credentials, which are alias, keystore password, and key password.

To sign the instrumented app, complete the following steps:

1. In your command line tool, open the directory where you have installed android-build-tools, and run the following command:

     zipalign -p 4 <path-to-patched-apk> <new-path.apk>
   

2. Sign the app with the keystore using the following command:

     # command if you are using keystore
   apksigner sign -v —ks <path-to-keystore> —ks-key-alias <alias> —ks-pass pass:<password> <new-path.apk>
   
     # command if you are using certificates
   apksigner sign --key release.pk8 --cert release.x509.pem <new-path.apk>
   

After you sign the instrumented app, the apksigner tool returns the signed instrumented app, new-path.apk. You can upload this app as an Enterprise user and run your tests.