Block reference / UI Interaction

Find text (dump)

Look for text among the screen's elements, and say whether it is there or tap it.

Only inWarpX Phone

Find text (dump) looks for text the app writes as text: a button's label, a message, a status. It reads the screen's elements, the same list a dump of the screen holds, so it is fast and exact, and it needs no selector, only the words. For text drawn into a picture or a game, use Find text (OCR); to name one element precisely, Element exists or Touch.

Find text (dump) finds the element whose text is exactly Allow, and taps it.
The Find text (dump) block's settings, filled in as in the example below.

Settings

Text

The text to look for. It can hold a reference such as {{variables.label}}.

ExampleAllow
Match

Exactly this text needs an element whose whole text is this, with the same capitals. Contains this text finds it inside a longer text and ignores case.

ExampleExactly this text
Then

Only say whether it is there answers true or false. Tap it also taps the first element that shows the text.

ExampleTap it
Wait up to (ms)

How long to keep looking, from 0 (look once) to 120000. The default is 5000.

Example3000
Fail when it is not found

On, the block fails with "Allow" is not on the screen when the time runs out. Off (the default), it answers false and goes on.

ExampleUnchecked
Save the answer (true / false) to a variable

Also stores the answer, true or false, in a workflow variable.

ExampleChecked
Variable namewhen Save the answer (true / false) to a variable is on

The variable to write. Later blocks read it as {{variables.permissionAsked}}, for example in a Conditions path.

ExamplepermissionAsked
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 for 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 true when the text was found (and tapped, with Tap it), false when it was not, as {{prevBlockData}} and in the variable when asked. Leaves by its single output either way.

Example: Allow notifications when the app asks

  1. Start
  2. Start app
  3. Find text (dump)
  4. Touch
Where Find text (dump) sits in the example workflow.
  1. Pick the phone in the editor's toolbar and add a Start app block for the shop app.
  2. Add a Find text (dump) block with Text Allow, Match Exactly this text and Then Tap it.
  3. Set Wait up to (ms) to 3000 and leave Fail when it is not found off, so a phone that never asks carries on.
  4. Add the rest of the flow after it and press Run: the dialog is answered when it shows, and passed over when it does not.

Good to know

  • Element blocks read the screen through the WarpX agent, which the Devices page installs on the phone. Without it the block fails with AGENT_NOT_INSTALLED.
  • It sees what the app exposes as text. A game, a picture or a page drawn its own way has none; use Find text (OCR) there.
  • Tap it touches a point inside the element that holds the text. A button's label is often a text inside the button, and touching it presses the button.
  • A field's own hint, such as Search, may count as its text while the field is empty.

See also

  • Find text (OCR) — Look for text in the picture of the screen, and say whether it is there or tap it.
  • Element exists — Whether an element is on the phone's screen: true or false.
  • Swipe & check screen — Swipe until something shows, or swipe once and say whether the list has ended.
  • Touch — Tap, hold or double-tap an element on the phone's screen, or a point on it.