Skip to main content

Actions with Application

Please read the Material Usage Rules on this site.

Let's go over the available functions for working directly inside the virtual machine. For example: installing apps, launching, stopping, running console commands (ADB Shell), and more.

How to add it to the project?​

Right-click → Add action → Android → Actions with Application

Add to project

Available actions.​

Install application.​

Install an app

This action lets you install an app from an APK file. Supported formats: .xapk, .apkm, .apks

Uninstall application.​

Uninstall an app

This action removes an installed app by its name, which you can find using the Installed Apps tool.

Open application.​

Open an app

Lets you launch an app you've already installed.

Open URL.​

Open URL
Lets you open a web page in a browser.

  • URL. This is where you enter the web page address you want to open.
  • App name. Put in the name of the app that can open links. You can find it using the Installed Apps tool. If you leave it blank, the page will open in the default browser.

Close application.​

Close an app

Closes an app (similar to the command adb shell am force-stop com.package).

Application cleanup.​

Use this action to wipe all user data.

Clear app data

If you check Clear only cache, only the cache will be deleted, leaving everything else intact.

Saving of application's data.​

This action saves all app data.

Save app data

Available parameters:​

  • Application name. You can find it using the Installed Apps tool.
  • Path to archive file. Here you need to enter the path where the archived app data will be saved (archive format is tar.gz).
Best practice.

Before saving data, it's best to close the app by using the Keyboard Emulation action with this text: {AndroidKeys.HOME}. This emulates pressing the HOME button.

Why close the app before saving data?​

If the app is open while you're saving its data, some files might still be in memory and not in the file system, so they might not get saved. Also, you shouldn't close the app with the Close app action for this purpose, as it kills the process abruptly and could result in data loss.

Restoring of application's data.​

This lets you load app data previously saved using the Save app data action.

Restore app data

Available parameters:​

  • Application name. You can find it using the Installed Apps tool.
  • Path to archive file. Enter the path to the archive with the saved app data.
Attention.

The app must be installed in the system but not running when restoring its data!

Get apk of the application.​

Get the app's apk

This action lets you extract the installation file for an app in .apk or .apks format. You can later install the app using the Install apk action.

Get cookies from the app.​

Get cookies from the app

This action collects cookies from apps that display web content; the cookies are returned in json format. You can then work with this data using the JSON and XML processing action.

Get notifications.​

Get notifications

This action fetches notifications from the app notification shade (top panel) in json format. You can then process this data using the JSON and XML processing action.

Clear notifications.​

Clear notifications

This feature clears all accumulated notifications from the top panel.

Name of the active application.​

Name of the active app

This action lets you get the name of the app that's active and in the foreground on your device.

Get application list.​

This action gets the names of all installed apps and saves them to a list.

Get the list of apps

Filter options for apps:​

  • All. All apps installed on the device.
  • System. Pre-installed system apps, which are usually not removable (only hidable).
  • User. Apps you've installed yourself.

Application already installed.​

Check if the app is already installed

This action checks if an app is installed on the device. If it's missing, the process will go down the error branch.

Get accounts​

Get accounts
Returns the accounts added on the device in JSON.

Available parameters:​

  • Application name. The app the accounts are asked from. The field is required. You can find the name using the Installed Apps tool.
  • Account type. Selected - accounts of the given type only, e.g. com.google. All - accounts of any type.
  • Save the result to a variable. Receives a JSON array: name, type, password and metadata for every account. The metadata from this result is what the Add account action expects.
Root is required.

Add account​

Add account
Adds an account to the device.

Available parameters:​

  • Account name. Typically an email address.
  • Account type. For example com.google.
  • Account password. Goes in encrypted, exactly as the Get accounts action returns it - a plain-text password will not do. An empty field means no password is set.
  • Account metadata. The extra data of the account exactly as the Get accounts action returned it: that is what carries the account, authorisation and all, to another device. Arbitrary text or your own JSON will not do.
Root is required.

Remove account​

Remove account
Removes an account from the device.

Available parameters:​

  • Account name. Selected - one account is removed. All - every account of the chosen type is removed.
  • Account type. Selected - accounts of the given type only. All - accounts of any type.
Root is required.