Terminal
Terminal/Skill
Common issues, Developer Mode, version compatibility, state machine diagnosis
By Meta
Works with
npx skills add facebook/meta-wearables-dat-ios --skill debuggingDiagnose common setup, registration, and streaming issues in DAT SDK integrations.
If local DAT Inspector MCP tools are available, use the live-debugging-mcp
skill before changing app code. Prefer get_dat_readiness,
get_companion_boundary_diagnosis, and get_device_path to separate app bugs from
Meta AI app/device boundary issues using read-only DAT evidence.
Device not connecting?
│
├── Is Developer Mode enabled? → Enable in Meta AI app settings
│
├── Is device registered? → Check registration state
│
├── Is device in range? → Bluetooth on, glasses powered on
│
├── Is the app registered? → Check registrationStateStream()
│
└── Stream stuck in waitingForDevice? → Check device availability
Developer Mode must be enabled for 3P apps to access device features.
waitingForDevicestopped → waitingForDevice → starting → streaming → stopped
Ensure compatible versions of SDK, Meta AI app, and glasses firmware. See version dependencies for the current compatibility matrix.
| Issue | Workaround |
|---|---|
| No internet → registration fails | Internet required for registration |
| Streams started with glasses doffed pause when donned | Unpause by tapping the side of the glasses |
| A single touchpad tap pauses an active stream | Tap again to resume; keep the last frame on screen while StreamState is .paused |
See the public known issues page for the current list.
import os
private let logger = Logger(subsystem: "com.yourapp", category: "Wearables")
// In your streaming code:
logger.debug("Stream state changed to: \(state)")
logger.error("Stream error: \(error)")
When the developer has a local DAT debug server connected to the agent:
get_sdk_state and get_dat_readinessget_companion_boundary_diagnosis for permission, app identity, device
capability, device-selection, deeplink-return, and DAM/DWA-visible blockersget_device_path to trace app -> DAT registration -> Meta AI app permissions ->
device selection/link -> session -> streamwait_for_events with the
narrowest category or source that matches the flowexport_diagnostic_bundle for redacted support handoffDo not treat this as companion app introspection. It is diagnosis from app-visible DAT debug events.
MWDAT > AppLinkURLScheme matches itmetaWearablesAction links to Wearables.shared.handleUrl(_:)processing, bluetooth-central, bluetooth-peripheral, external-accessory)UISupportedExternalAccessoryProtocols contains com.meta.ar.wearableNSBluetoothAlwaysUsageDescription, NSLocalNetworkUsageDescription, and NSBonjourServices present