For native application replay and hybrid replay, the images that you added to your application should be copied to the replay server. When the images are on the replay server, they don't need to be sent in the payload, which could cause performance issues. Replay uses a unique identifier for each image and retrieves only the needed images from the replay server.

There are different tools that can be used for capturing images.

Target Simulator

Target Simulator is a command line program that runs on your local machine and acts as a Acoustic Tealeaf target page to collect the images in your application. The tool assigns unique identifiers to the images and collects them in a folder.

The Target Simulator tool can be used with the Android SDK and iOS SDK. However, it should be used only with the Android SDK when the Android Image Capture tool does not support your replay experience. It can be used in both Windows™ and iOS environments.

Android Image Capture

The Android Image Capture tool is used with the and only runs in Android environments. It should be the primary tool that you use to capture images in your application for Android environments.

The Android Image Capture tool is a command line program that automatically collects all images in an Android application to an archive folder called images. The tool extracts and creates proper filepath mapping from your APK file so that the metadata collected from the Android client library for images can display properly.

More information from the Acoustic developer center

• Collecting images from your application with the Target Simulator for iOS
• Capturing and uploading images for application replay with the Android Image Capture tool
• Collecting images from your application with the Target Simulator for Android

Uploading native replay images and templates

Use this procedure to upload the native replay files for iOS and Android images and templates for your organization.

Before you begin

Use the upload procedure described here when your organization is empty of replay assets.

After you upload assets using the procedure described here, you can use the Asset Manager feature to manage (view, delete, download, and upload) individual assets.

Before you can upload the native replay images and templates for iOS and Android, you must collect the image and template files from the application.

• For iOS applications, run the TLF image tool that is located here:

  https://github.com/ibm-watson-cxa/SDK_Tools/tree/master/SDKPackages/tealeaf/ios/TLFImageTool/TLFImageTool.app/Contents.

• For Android applications, run the Android image capture tool that is located here:

  https://github.com/ibm-watson-cxa/SDK_Tools/tree/master/SDKPackages/tealeaf/android/AndroidImageCaptureTool.

• For dynamic images, run the Target Simulator tool that is located here:

  https://github.com/ibm-watson-cxa/SDK_Tools/tree/master/TealeafTargetSimulator.

You can obtain the base templates here:https://github.com/ibm-watson-cxa/SDK_Tools/tree/master/NativeTemplates/tlt

You can upload the image and template package files to the system as .zip files.

1. Log in as the Organization Administrator.
2. Click Admin.
3. Select Company settings.
4. Click Edit.
5. Find the Native replay files section of the screen.
6. Click Image package Upload file.
7. Browse to the file location and select the file.
   You can upload the file as a .zip file.
8. Click Upload.
9. Click the Template package Upload file link.
10. Browse to the file location and select the file.
    You can upload the file as a .zip file.
11. Click Upload.
12. Click Save.

What to do next

You can use the asset manager to browse read-only versions of the native image files that you uploaded. You can also use asset manager to download, delete, and upload individual files. For information on how to use the asset manager, see Manage replay assets from asset manager.