← All use cases

Debug in iOS simulator

Use ZeroTwo with XcodeBuildMCP to operate your app in iOS Simulator, gather evidence, and work toward a fix.

ZeroTwo finds the correct Xcode scheme and simulator, starts the app, reads the UI tree, taps, types, swipes, and grabs screenshots and logs, converting a fuzzy bug report into a small fix that has been verified.

Advanced
1h

Skills & Plugins

  • Build iOS Apps
    Builds and drives your app in the simulator, capturing logs, screenshots, and stack traces to narrow a bug (desktop app; needs a Mac with Xcode).

With the Build iOS Apps plugin, ZeroTwo can run the reproduce, debug and verify loop in iOS Simulator, collecting the evidence a person would gather by hand. It works in the desktop app on a Mac with Xcode, and it suits one concrete UI or crash bug at a time.

Give ZeroTwo the whole simulator loop

Let ZeroTwo pick the target, launch the app, follow the repro steps, capture screenshots and logs, patch the code, and replay the same path to confirm the fix. The Build iOS Apps plugin drives this through XcodeBuildMCP. If no project, scheme, or simulator is chosen yet, ask ZeroTwo to find and reuse them for the session; it asks you to boot a simulator if none is running.

Leverage what XcodeBuildMCP can do

The plugin turns on XcodeBuildMCP's simulator, UI automation, debugging and logging workflows. Four capability groups are worth naming in the prompt:

  • Discovery: project or workspace, schemes, and finding the booted simulator.
  • Build and launch: build, install, relaunch, resolve the bundle id.
  • UI inspection: accessibility tree, screenshots, taps, typing, scrolling, gestures.
  • Logs and debugging: simulator log capture and the debugging workflow.

Ask ZeroTwo to read the view tree before tapping, so it targets labels or IDs rather than raw coordinates.

Turn a vague bug into a reproducible script

Give one concrete bug and its expected outcome, mention any login, deep link, or fixture once, and let ZeroTwo pause only when blocked.

Practical tips

Ask for evidence, not just a fix

Request the simulator, scheme, screenshots, log excerpts, and any stack details behind the diagnosis so the patch is easy to review.

Prefer accessibility labels over coordinates

If ZeroTwo must tap by coordinates, it should say so; that often means the fix also needs a testability tweak.

Keep one bug per run

Finish a single reproduce-fix-verify cycle before moving to related issues.

Related use cases