Block reference / App Management

Uninstall app

Remove an app from the phone, with or without its data.

Only inWarpX Phone

Uninstall app removes an app from the run's phone. By default its data goes with it; Keep its data leaves the data behind, so the same app installed again finds its settings and sign-in. Use it to swap a broken build for a good one, or to take an app off every phone in a farm.

Uninstall app removes Example Shop and its data; its icon leaves the home screen.
The Uninstall app block's settings, filled in as in the example below.

Settings

Package

The app, by its package name, such as com.shopee.vn. As you type, the field suggests the apps on the phone picked in the editor's toolbar, the apps phone farms run most (typing zalo finds com.zing.zalo) and the packages the workflow already names; tick System apps in the list to include built-in ones. What you type is kept as typed, so a reference such as {{loopData.package}} works too.

Examplecom.example.shop
Keep its data (an app installed again finds it)

Removes the app but leaves its data on the phone. Installing the same app again later picks that data up.

ExampleUnchecked
Delay (ms)

A pause after the block finishes, before the next block starts. Write one number such as 1000, or a range such as 1000,3000 to pick a random pause in that range on each run.

Example0

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Hands on the package name as {{prevBlockData}}. Leaves by its single output.

Example: Replace a test build with the library's version

  1. Start
  2. Uninstall app
  3. Install app
  4. Start app
Where Uninstall app sits in the example workflow.
  1. Add an Uninstall app block with Package com.example.shop and leave Keep its data off.
  2. Add an Install app block with From on The APK library, by package and the same package.
  3. Add a Start app block to open the freshly installed app.
  4. Run it on each phone that had the test build.

Good to know

  • When Android refuses, for example for an app that came with the phone, the block fails with UNINSTALL_FAILED and the package manager's answer. An app that is not on the phone fails the same way.
  • The WarpX agent cannot be removed by a workflow; remove it from the Devices page.
  • A workflow that was not edited on this computer (from the Appstore, a file or the assistant) asks you to allow this block before its first run, in a window that lists what it will do. Blocks you set up in the editor are approved as you edit them, so your own workflows never ask; changing the block's settings asks again.
  • There is no Device field: the block acts on the run's phone — the one picked in the editor's toolbar, or each phone ticked for Run automation in the Control Center or named in an API run.

See also

  • Install app — Install an app from an .apk on this computer, from the APK library, or from Google Play.
  • Clear app data — Wipe everything an app stored on the phone, which signs it out.
  • Is app installed — Answer whether an app is on the phone: true or false.