What problem does it solve?
Debugging an iOS app built with the Meta Wearables Device Access Toolkit is hard when failures happen across the app, Meta AI companion app, and glasses boundary. This Skill gives an agent a structured, evidence-first workflow to diagnose registration, permission, session, and streaming failures using a local DAT Inspector MCP debug server instead of guessing from code alone.
Core Features & Use Cases
- Live runtime diagnosis: Connect to a running app's debug server and inspect connection status, SDK state, and DAT readiness before changing any code.
- Boundary and permission analysis: Inspect companion-app boundary diagnosis, device path, permissions, and device properties to separate iOS system issues from Meta AI app/device issues.
- Event-driven evidence gathering: Wait for targeted events by category or source, collect errors and event digests, and export a redacted diagnostic bundle for handoff.
- Use Case: A developer reports their app cannot stream from Meta AI glasses. The agent connects to the debug server, finds registration is blocked, and identifies a misconfigured Info.plist URL scheme and incomplete handleUrl(_:) callback as the cause.
Quick Start
Ask the agent to debug why your iOS DAT app cannot connect to the glasses using the local DAT Inspector MCP tools.