# 0.6.2

Released 11 November 2026.

Fixes for 0.6.1. A tap waits until your app's JavaScript is free and fails when the app doesn't react, a check sees only what is on screen, touches from two Squiggles or Studio take turns, and when your app never connects Squiggle says why. Studio's update relaunches Studio by itself.

Some flows that passed in 0.6.1 now fail, because the step now proves what it says. A tap your app doesn't react to fails with "the tap did nothing": mark a tap that is meant to change nothing `optional: true`. A tap's `expectRoute` fails when the app doesn't reach that screen within 5 seconds. A combined `waitFor` waits for every condition you give. `role: AXButton` also matches your app's own buttons, so two buttons with the same label are reported as ambiguous. `text` no longer matches part of a longer text your app shows, in checks and taps alike, and `label` has to match the whole accessibility label. A react-native-pager-view page that isn't showing is no longer visible or tappable. In a monorepo, an app with its own `.squiggle` folder is now its own project.

## Desktop app

- **Fix**: the update card shows when a release was published in your own time zone ("yesterday at 20:57"), shows progress as soon as you press **Update now**, and relaunches Studio on the new version by itself; a second press no longer closes the card, an error stays on screen, and **Later** keeps **Update available** in the title bar
- **Fix**: the Updates row in Settings says when an update is downloading, installing or waiting to relaunch

## CLI

- **Fix**: when your app never connects, Squiggle tells apart a bundle that is still building (it waits, and says so), a bundle without the Squiggle SDK (it says how to add it), a bundle that includes the SDK but never ran it, and a Metro that is up but slow, instead of pointing you at a red box or a stopped Metro
- **Fix**: `squiggle doctor` waits up to 30 seconds for your app on a simulator, longer while Metro is still building the bundle, and says when the bundle has no Squiggle SDK, instead of waiting forever
- **Fix**: on a heavily loaded Mac, Squiggle waits longer for its agent to start in your app, and if it still doesn't answer, says the agent is slow and gives the load average, instead of telling you to reinstall; an app that quits right after launching is reported as such
- **Fix**: a run whose app crashed says so, with the exception, where it happened and the crash report's path; crash reports are matched to the simulator the run used, so another session's crash of the same app is no longer stored with your run or listed by `squiggle perf crashes`
- **Fix**: `squiggle probe eval` and the other probe commands print `E_JS_BUSY` or `E_JS_UNOBSERVABLE` and exit 2 when your app's JavaScript stays busy or Squiggle can't find its process, instead of reporting a Squiggle crash
- **Fix**: `squiggle agent validate` blocks a flow only on a recording of an earlier run of that same flow, not on an incident or another flow's recording; a screen it learned under an older short name counts as seen; and it reports a `runFlow` file it can't find
- **Fix**: in a monorepo, an app that keeps its own `.squiggle` folder (with a `config.jsonc`, flows or interfaces) is its own project, so `squiggle flow`, `squiggle contracts` and the MCP server read it without `SQUIGGLE_PROJECT_ROOT`; `squiggle init` writes into whichever folder the app already uses
- **Fix**: `perf.db` cleanup works in small steps, so other Squiggle processes writing the store no longer wait seconds or lose writes; if another process does keep it locked, a run prints one line naming the processes instead of one "database is locked" line per write
- **Fix**: a run that loses its app to an MCP server started before you updated Squiggle names it as an older version and tells you to update it

## Agents & MCP

- **Fix**: `launch_app` with `relaunch: "always"` relaunches an app that is stuck before its JavaScript loads, such as on the Expo development launcher, and `run_flow` takes `fresh: true` to do the same before a run
- **Fix**: `status` and `screenshot` work with no app connected, and `status` says why nothing is
- **Fix**: the `tap` tool takes `expectRoute` and answers `ok: false` when the app doesn't reach that screen
- **Fix**: `run_flow` names a failed sub-flow's step as `failedStep`
- **Fix**: `run_flow` can remove a row the run created, such as a queued prompt, when your app's buttons render an inner button with the same test ID and label
- **Fix**: the watch skips recording an incident for disk space only when the disk holding your project has less than 2 GB free, and says how much was free; a recording that can't be saved for another reason says that reason instead of "low disk space"

## Flows & device

- **Fix**: a tap waits, for up to three seconds, until your app's JavaScript is free and the renders it was working on have landed, so it no longer lands on a busy screen; an idle app pays nothing
- **Fix**: a tap on one of your app's controls that gets no reaction to either touch fails with "the tap did nothing" and shows what was under the finger each time, instead of passing with a warning
- **Fix**: a tap with `expectRoute` fails when the app doesn't reach that screen within 5 seconds after the tap lands; before, a tap didn't check it, so a tap that pressed the wrong control, or nothing, passed
- **Fix**: a combined `waitFor` passes only once every condition holds at the same moment, and a timeout says which ones did; `appRunIdle` waits on its own, like `visible` and `ms`
- **Fix**: `text` matches the same way in checks, waits, conditions and taps: in your app it has to match a whole text, and a styled run inside a sentence counts as its own text. Text your app draws natively, or that another app draws (a file picker cell, a natively rendered markdown paragraph), still matches when its accessibility label contains it. So `notVisible: { text: Needs attention }` passes while a card reads "1 needs attention", and a tap on that text doesn't tap the card
- **Fix**: `label` always has to match the whole accessibility label, in any case
- **Fix**: a selector's `role` matches in either naming: `AXButton` matches your app's buttons as well as iOS's, and `button` matches a native alert's buttons; `AXImage` and `image`, `AXSwitch` and `switch`, and `AXSlider` and `slider` pair the same way
- **Fix**: with the 0.6.2 SDK, a button you put in the iOS 26 bottom toolbar with `Stack.Toolbar.View` is tapped where it is drawn after a JavaScript reload too, instead of at the top of the screen
- **Fix**: with the 0.6.2 SDK, a react-native-pager-view page that isn't showing (react-native-tab-view uses one too) is no longer on screen to Squiggle: `visible` fails for a control on it, `describe` leaves it out, and a tap on it fails as not found
- **Fix**: `scrollUntilVisible` no longer drags when its element is already on screen but still moving, for example right after a tap turns a pager, so the pager stays on the page you opened
- **Fix**: `back` waits for an app that reports its new screen late before judging the result, so it no longer says the screen didn't change, or taps a back button on the screen it already returned to
- **Fix**: a `runFlow` file not found beside the flow that names it is looked up in `.squiggle/flows`, and a missing one fails with the paths it tried; a failed sub-flow, loop, branch or retry names the step that failed, with its kind, selector and message
- **Fix**: a `network.stub` step right after `launchApp: { relaunch: always }` reaches the relaunched app; a stub step that fails says whether the app runs without network capture or its Squiggle agent didn't answer
- **Fix**: an in-app browser opened full screen lists its Done button and Format Options, and a tap on controls iOS draws over your app (an in-app browser, a share sheet, a system alert) is about a second faster
- **Fix**: Squiggle's taps no longer leave a finished touch behind in your app, which could crash it in iOS's gesture handling when a real tap, such as one on an alert button, followed
- **Fix**: touches from two Squiggles, or from Squiggle and Studio, take turns on a simulator, including touches sent through the simulator itself (alerts, sheets, system buttons); one that waits more than 2.5 seconds fails with `input-busy` instead of pressing anyway
