// Common issues, Developer Mode, version compatibility, and session and stream diagnosis
Session and Stream capability setup, video frames, photo capture, resolution and frame rate configuration
Kotlin patterns, DatResult, session and capability conventions for DAT SDK Android development
Display capability setup, display-capable device selection, UI DSL, icons, buttons, images, and video playback
SDK setup, Gradle integration, AndroidManifest configuration, and first connection to Meta glasses
MockDeviceKit for testing without physical glasses hardware
App registration with Meta AI and device permission flows
| name | debugging |
| description | Common issues, Developer Mode, version compatibility, and session and stream diagnosis |
Diagnose common setup, session, and stream issues in DAT SDK integrations.
No eligible device or session won't start?
|
+-- Did you call Wearables.initialize(context)? -> Must happen before SDK usage
|
+-- Did registration complete? -> Observe Wearables.registrationState
|
+-- Is Developer Mode enabled? -> Enable it in the Meta AI app for dev builds
|
+-- Does Wearables.devices contain a linked device? -> Check Bluetooth and range
|
+-- Did createSession() or addStream() return a DatResult failure? -> Surface the typed error
Developer Mode must be enabled for local development builds that use APPLICATION_ID = 0.
Wearables.createSession(...) fails with no eligible deviceAPPLICATION_ID and release-channel gating insteadSTARTEDWearables.registrationStateWearables.devices contains a compatible linked deviceSTREAMINGsession.start() succeeded before calling session.addStream(...)Wearables.checkPermissionStatus(...)stream.start() returned successcapturePhoto() only succeeds while the stream is actively streamingCaptureError instead of discarding the DatResultEnsure compatible versions of the SDK, Meta AI app, and glasses firmware. See version dependencies for the current compatibility matrix.
private const val TAG = "DATWearables"
stream.start()
.onFailure { error, _ -> Log.e(TAG, "Failed to start stream: ${error.description}") }
Prefer logging typed DatResult failures and observed state transitions over generic exceptions.
Wearables.initialize(context) ran before SDK usageAPPLICATION_ID matches the build modeDatResult failures are surfaced in logs or UI