ios-debugger-agent

To debug an iOS app on a booted simulator, you need to build the project scheme, launch the app, inspect the UI state, perform interactions, and capture runtime logs for diagnostics.

Yes, iOS simulator UI inspection allows you to capture screenshots and collect console logs. This enables you to perform taps and types on the interface for post-mortem runtime diagnosis.

Automating UI interaction testing for an iOS project scheme involves launching the app on a booted simulator, describing the UI state, and programmatically performing taps and types to verify interface behavior.

Using XcodeBuildMCP tools is required to control the booted simulator, build the project scheme, run the app, and collect logs for reliable simulator-based testing and diagnosis.

The best way to diagnose iOS simulator failures is to capture console output and logs during the app session. This log-based diagnosis helps identify issues after performing build, run, and UI interactions.

Debugging session failures often occur when a simulator is not properly booted or project scheme defaults are misconfigured. You must identify the booted simulator and set session defaults before building.