ios-emulator

Automates iOS simulator interactions via the steve CLI for app testing and UI verification.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill ios-emulator-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-emulator
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/ios-emulator
Command: npx skills add https://github.com/fedixyz/fedi --skill ios-emulator-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually testing iOS app behavior in the simulator is slow and error-prone. This Skill lets you programmatically launch apps, tap UI elements, read accessibility trees, and capture screenshots to verify app behavior without manual interaction. ## Core Features & Use Cases - UI Automation: Launch apps, tap elements by accessibility text or coordinates, swipe, and type into focused fields using the steve CLI. - State Verification: Read normalized accessibility trees and capture screenshots to confirm navigation and layout after each action. - Parallel Simulator Support: Target specific simulators by UDID with separate Appium sessions per device, bundle, and port. - Use Case: After building the Fedi React Native app, launch it in the simulator, tap "Get started", and verify the onboarding screen renders correctly via the accessibility tree and a screenshot. ## Quick Start Use the ios-emulator skill to launch the app in the iOS simulator and verify the home screen loads correctly.

Frequently Asked Questions about ios-emulator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tapping buttons in an iOS simulator?

Use the steve CLI with the tap command followed by the exact accessibility text, such as steve tap "Continue". For unlabeled elements, pass coordinates from the accessibility tree bounds, like steve tap 200,780.

How to verify iOS app UI after an automated action?

Chain steve commands with && to act then verify: run steve tap "Button" && steve a11y && steve screenshot /tmp/s.png. The a11y and screenshot commands auto-wait for idle, so no manual sleep is needed.

Can I run multiple iOS simulators in parallel for testing?

Yes, pass --device <UDID> on every steve command to target a specific simulator. Steve maintains separate Appium sessions per device, bundle, port, and headless mode, enabling parallel agent workflows.

Why does tapping by text fail on some iOS screens?

The tap command uses exact-match accessibility text only, and some controls are exposed only by coordinates or IDs. Always run steve a11y first on unfamiliar screens to find the exact text or bounds before tapping.

What should I do when the iOS simulator gets into a bad state?

Use steve stop to terminate the app, steve restart to relaunch without clearing the Appium session, or steve reset to uninstall and reinstall the bundle. Avoid random taps to recover from broken states.