← Node guide
App

Install App

Puts a build on the phone — one you upload, or one at a URL the device can reach.

app.install
The piece

Install an .apk / .ipa onto the device (upload a local build or paste a URL)

Reach for it when

  • Testing the build your pipeline just produced.
  • Starting from a known state: uninstall, then install, then run.
Install App
Idle
In the bag

Every setting this block has. A field marked only when appears once you have chosen the mode above it — those are alternatives to each other, not extra things to fill in.

  • App build (.apk / .ipa)Required
    starts at —

    Upload a local build or paste a reachable URL — Appium downloads & installs

  • Package / Bundle ID (optional)
    starts at —

    Auto-detected from an uploaded .apk / .ipa. Used by Launch-after-install and later Launch / Verify steps

  • Launch after install
    starts at on

    Open the app right after installing. Turn off when the next step is what should open it (a deep link, a notification).

Build it

  1. Give it the build

    Upload an .apk or .ipa, or paste a URL and let the device download it. A CI trigger usually means the URL is already the artifact your pipeline published.

    Install AppSettings
    App build (.apk / .ipa)Required
    app-release.apk
    Package / Bundle ID (optional)Read out of the upload
    com.acme.shop
    Launch after installDefault
    on

  2. Let it open the app for you

    Launch after install is on by default: it saves a Launch step, and more usefully it means the very first thing the run does is prove the build starts at all. Turn it off when the next step has to be what opens the app — a deep link test, where an app already on screen would hide whether the link worked.

    InstallingCcom.acme.shopinstall, then open it
    install, then open

  3. Use the id it found

    An uploaded build has its id read out of it, so every later App step can reference this one instead of you typing the package name four times.

    Install App
    Verify Installed
    Launch / Activate
What comes out
  • The package / bundle id that was installed — the field every other App step wants.
  • Whether the install replaced an existing copy or was a first install.
Watch out
  • An .ipa has to be signed for the device it is going on. An unsigned build fails at install, not at launch.
  • Installing over an existing copy keeps its data. For a true first-run test, Uninstall App first.
Usually next to
Verify InstalledLaunch / ActivateUninstall App