meta-wearables-dat-ios

When the glasses run out of available memory, all active streaming and capture flows start failing silently. No explicit error is returned, no failure callbacks are triggered, and the SDK does not surface any recoverable or terminal error state. From the application side, operations appear to be running normally, but: • video / audio streams stop producing data • capture requests do not complete • no reasonable error or warning is emitted to indicate an OOM condition This makes the issue extremely hard to detect and debug, as the system enters a broken state without any signal to the developer. The example application in this repository can also reproduce this behavior under memory pressure, which suggests this is a systemic SDK-level issue rather than an app-specific bug. Expected behavior • Explicit error or callback when memory limits are reached • Clear indication that streaming/capture failed due to OOM • Ability to gracefully stop, recover, or restart affected flows Actual behavior • Silent failure with no error reporting • SDK remains in an unrecoverable state until restart

Summary When is called without Developer Mode enabled in the Meta AI app, the SDK fails completely silently: Registration state transitions from → → back to No error is thrown (the returns without error) No is raised No console log or warning from the SDK The Meta AI app never opens for OAuth This makes debugging extremely difficult. We spent hours investigating WebSocket issues, Info.plist configuration, portal settings, and URL handler code before discovering the root cause was simply that Developer Mode wasn't enabled. Steps to Reproduce 1. Install the Meta AI app on iPhone (v254+) 2. 2. Do NOT enable Developer Mode (Settings → App Info → tap version 5x) 3. 3. Configure a new iOS app with MWDAT SDK v0.4.0 4. 4. Set to empty string in Info.plist (Developer Mode config) 5. 5. Call Expected Behavior The SDK should provide clear feedback* when registration cannot proceed. For example: Throw a with a message like: "Developer Mode is not enabled in the Meta AI app. Enable it in Settings → App Info → tap App version 5 times." Or at minimum, log a warning to the console explaining why registration failed Actual Behavior returns without error Registration state briefly goes to then silently reverts to No error, no log, no indication of what went wrong The Meta AI app never opens — the OAuth flow never starts Environment MWDAT iOS SDK: 0.4.0 Meta AI app: v254+ iOS: 18 Xcode: 16 Suggestion A descriptive error message here would save developers significant debugging time. The SDK clearly knows whether Developer Mode is active — surfacing that as a thrown error or at least a console warning would be a huge improvement. Similarly, it would help to have better error messages for other silent failure modes we encountered: Wrong/empty Bundle ID in the Wearables Developer Center portal → silent fail Wrong/empty Team ID in the portal → silent fail MetaAppID set to actual app ID instead of empty string* while in Developer Mode → silent fail All of these cause the same symptom (registering → available, no error) and could benefit from explicit error messages.

Hello, I was trying to put out a build of my app on testflight with DAT, but the binary is invalid. Here is the exact email I got, but the gist is the sdk needs a privacy manifest ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/MWDATMockDevice.framework/MWDATMockDevice”, which includes nanopb, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. ITMS-91065: Missing signature - Your app includes “Frameworks/MWDATMockDevice.framework/MWDATMockDevice”, which includes nanopb, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

Creating issue for investigation. Will update if bug/help after that. Discussed in https://github.com/facebook/meta-wearables-dat-ios/discussions/85 Originally posted by mitdave95 February 10, 2026 Not sure if this is intended behavior or a bug, so sharing here for clarity. After updating to 0.4.0 on HSTN and Displays, I’ve observed that only one developer app can stay registered at a time. Registering a new app automatically unregisters the previous one, which then requires going through the full registration flow again. I’ve attached videos demonstrating the behavior. Would appreciate confirmation on whether this is expected or something that needs investigation. https://github.com/user-attachments/assets/400e142f-3208-4acc-ae65-9fbe1eb97888