meta-wearables-dat-android

Hello, Please reference issue https://github.com/facebook/meta-wearables-dat-android/issues/108 for the bulk of it, but the main parts are this. When I try to connect my glasses to my own application, I'm unable to and keep getting issues related to connectivity. Weather that's because it thinks I need to update the DAT application or because it cannot find my glasses or some other connectivity. I'm trying to get this resolved and I've been waiting for close to a month apparently with no more response other than from three hours ago to let me know they were closing it. I have followed up many times, but nothing until three hours ago. I have tried to provide logs and explain what's happening, but nothing still. Thank you

Summary consistently fails with , even though phone-side registration is fully completed () and the SDK enumerates the glasses (). Logcat shows the glasses themselves report and , which suggests the app authorization for this device is never delivered from the server to the glasses — i.e. the phone-side gates all pass, but the glasses-side allowlist remains empty. Additionally, the Release Channel selector does not appear in the Meta AI app (device menu > Settings), even though the tester invitation has been accepted and https://wearables.meta.com/invites correctly shows the integration (GlassBridge / internal / 1.0.1) for this account. ## Environment ## What works (phone side) succeeds; + are read from the manifest correctly completes via the Meta AI app; reaches * (not just ) Camera permission granted as "Always allow" through contains exactly one device; glasses are paired, Bluetooth-connected, worn, and ## What fails The failure is immediate (~400 ms after the user taps "start session"), with no further diagnostic output from the SDK. Glasses-side state at the same time (from Meta AI app logs, device ): ## Developer Center configuration (all completed) Package name and app signature (base64url) registered Camera permission requested with rationale submitted Version 1.0.1 created and assigned to the internal* release channel Product listing complete (name, icons) Tester invitation sent to the Meta-account email, accepted, and confirmed visible at wearables.meta.com/invites ## Use case The app captures a photo only on an explicit user button press, to identify/describe the object the wearer is looking at (personal use, e.g. fishing trip logging). No background or covert capture — privacy-conscious, legitimate development. ## Related issues #81 — identical glasses-side signature ( + ), unanswered #94 — identical symptom set, including the missing Release Channel selector in the Meta AI app #99 — precedent where a maintainer checked the device's server-side channel state from the serial number and resolved the issue ## Request As in #99, could someone check the server-side channel/authorization delivery state for this account/device, and push the app authorization to the glasses if it is stuck? I'm happy to share the glasses serial number privately (omitted here since this is a public board) — please let me know the preferred channel. Thank you!

Summary Phone-side registration completes (), but glasses never receive authorization. App remains under "Developer mode apps" at bottom of App Connections, no Release Channel selector in Meta AI app. Identical to #115 / #99 / #120. Environment Application ID: Package name: App signature SHA-256 (first 8 chars): Build: — Status in Dev Center: Published to release channel Tester: invited with Meta account, Accepted at https://wearables.meta.com/invites Phone: Meta AI app: Glasses: Meta Ray-Ban Display, FW , DAT component What works success, and read from manifest (not 0) consent screen in Meta AI -> Connect -> , glasses paired, connected, worn Dev Center: 1 tester, Accepted, Build Ready -> Published What fails Meta AI app > Glasses > Settings (gear): No "Release Channel" entry at all App Connections: app stays at very bottom under "Developer mode apps" header, separate from Shazam/main list