
Debugging
- 5 installs
- 340 repo stars
- Updated August 3, 2026
- facebook/meta-wearables-dat-android
Diagnoses common DAT SDK Android setup, session, and stream issues covering initialization, registration, Developer Mode, and device eligibility.
About
Provides a diagnostic flow for common DAT SDK Android problems like no eligible device or sessions that won't start. Android developers use it to check initialization, registration state, Developer Mode, and typed DatResult failures.
- Decision-tree diagnosis for session/stream issues
- Covers Wearables.initialize, registration, Developer Mode
Debugging by the numbers
- 5 all-time installs (skills.sh)
- Ranked #828 of 1,039 Mobile Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/facebook/meta-wearables-dat-android --skill debuggingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 340 |
| Last updated | August 3, 2026 |
| Repository | facebook/meta-wearables-dat-android ↗ |
What it does
Diagnoses common DAT SDK Android setup, session, and stream issues covering initialization, registration, Developer Mode, and device eligibility.
Files
Debugging (Android)
Diagnose common setup, session, and stream issues in DAT SDK integrations.
Quick diagnosis
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 errorDeveloper Mode
Developer Mode must be enabled for local development builds that use APPLICATION_ID = 0.
Symptoms when Developer Mode is disabled
- Registration flow completes but the device never becomes eligible
- Permission requests do not succeed for development builds
Wearables.createSession(...)fails with no eligible device
Watch for
- Developer Mode may reset after app or firmware updates
- Developer Mode is configured per linked device
- Production builds use a real
APPLICATION_IDand release-channel gating instead
Session and stream issues
Session never reaches STARTED
- Verify
Wearables.registrationState - Check that
Wearables.devicescontains a compatible linked device - Ensure the glasses are powered on, unfolded, and in range
Stream never reaches STREAMING
- Confirm
session.start()succeeded before callingsession.addStream(...) - Check camera permission status through
Wearables.checkPermissionStatus(...) - Make sure
stream.start()returned success
Photo capture fails
capturePhoto()only succeeds while the stream is actively streaming- Surface the returned
CaptureErrorinstead of discarding theDatResult
Version compatibility
Ensure compatible versions of the SDK, Meta AI app, and glasses firmware. See version dependencies for the current compatibility matrix.
Logging
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.
Checklist
- [ ]
Wearables.initialize(context)ran before SDK usage - [ ] Developer Mode enabled for development builds
- [ ]
APPLICATION_IDmatches the build mode - [ ] Registration completed before session creation
- [ ] Bluetooth permission granted
- [ ] Camera permission granted through Meta AI
- [ ] Session and stream
DatResultfailures are surfaced in logs or UI