Meta Registration Connect Button Fails

[itsdanieltoth-ctrl]

Bug Report: Third-party DAT app registration hangs on
"Connect" (Ray-Ban Meta Gen 2)
Summary
Tapping Connect on the Meta AI app's third-party app consent screen does nothing. The button
grays out and the flow hangs indefinitely. No callback is delivered to the requesting app, no error is
shown. This reproduces with both a custom DAT app and is consistent with Discussion #42.
Environment
• Glasses: Ray-Ban Meta Gen 2
• Phone: Android (sideloaded DAT test app)
• Meta AI app version: 292.0.0.19.164 (latest from Play Store as of Sep 27, 2026)
• DAT SDK (phone): 1.0.0 (Maven Central, latest)
• DAT SDK (glasses): 1.0.0 — installed via Meta AI app → App info → Install (was "Not installed"
before)
• Developer Mode: ON (verified in Meta AI app)
Steps to Reproduce

1. Build any DAT app using Wearables.startRegistration() (tested with custom app using DAT SDK
   1.0.0, com.meta.wearable.dat:dat-core:1.0.0)
2. Call startRegistration() — the Meta AI app opens with the "unverified third-party app" consent
   screen
3. Flip the consent toggle ON
4. Tap Connect
5. Result: Button grays out, nothing happens. No rowansight:// callback (or equivalent deep-link) is
   ever fired. The requesting app's registrationState never leaves its pre-registration state. No error
   appears in the requesting app's registrationErrorStream.
   What Was Ruled Out
   • ✅ SDK initializes correctly in the requesting app (Glasses SDK ready, registrationState observable
   active)
   • ✅ Wearables.RequestPermissionContract() activity-result launcher registered properly in
   onCreate
   • ✅ rowansight:// deep-link scheme declared in manifest with matching intent-filter
   • ✅ ACDCRegistrationService declared in merged manifest (from DAT AAR)
   • ✅ Network connectivity confirmed (Wi-Fi on; DAT SDK glasses component downloaded and
   installed successfully)
   • ✅ Glasses restarted after DAT install; Meta AI app force-stopped and reopened
   • ✅ Phone restarted; Meta AI app cache cleared
   • ✅ No conflicting third-party DAT app installed (only one can hold the developer slot)
   • ✅ Phone has no Play Store update available for Meta AI app
   Additional Notes
   • The requesting app does not crash — it stays alive waiting for the callback that never comes.
   • The consent screen's toggle UI is responsive; only the Connect action hangs.
   • This matches the behavior in Discussion Unable to connect Meta Ray-Ban Gen 2 glasses – redirected to Meta AI app but nothing happens #42 exactly (Gen 2 glasses, latest Meta AI app, Connect
   does nothing, no result returned), except we also confirmed the on-glasses DAT SDK component
   installs correctly and the issue persists afterward.
   • The hang occurs inside the Meta AI app — the requesting app's code path after startRegistration()
   is just waiting on the callback intent.
   Expected Behavior
   Tapping Connect should complete registration and fire the callback deep-link so the requesting app
   can proceed to continueRegistration.
   Request
   Please confirm whether this is a known issue in Meta AI app 292.x and whether a fix is planned.
   Happy to provide ADB logs if you tell me what to capture.

[itsdanieltoth-ctrl]

Update: Oct 8–9 diagnostics — narrowed it down, still stuck at the same wall

Following up on the original report with everything we ran overnight:

v22 sanity check: the supposedly missing class turned out to be present in every build since v13, so we suspected a damaged installed copy — but a fresh v22 reinstall crashed identically. Bad download ruled out.

Diagnostic builds: we built three live X-ray versions and installed them one by one, screenshotting results on the phone:

• v23 — pops up a class-load PASS/FAIL report
• v24 — deeper X-ray of what the runtime actually sees inside the app
• v25 — sweep-loads all 10,000+ classes and reports every failure

v26 found the big one: 886 failing classes, almost all from Meta's own libraries. Root cause turned out to be our manual build (aapt2/D8 pipeline) missing the protobuf library that Meta's code needs. We added it in v27, which fixed 450 of the 886 failures.

Where we're stuck: three Meta service classes still will not load on this phone even though they are verified present and correct in the APK — we checked six different ways. In v30 we removed the broken service entirely to test registration without it, and the Connect button still bounced straight back to the registration page. So the remaining three unloadable classes don't appear to be the blocker either — the hang (now bounce-back) is happening on Meta's side of the handoff regardless.

Next steps from our end:

1. Rebuild with the proper Gradle toolchain instead of the manual build script, in case it packages Meta's classes differently — planned today. DONE Oct 10 (v31): full Gradle 8.9 + AGP build, protobuf-javalite bundled, broken service stripped via manifest merger rule, same signing key. Installed clean over v30.
2. v31 result: registration still fails — status UNAVAILABLE, error FAILED_TO_REGISTER, no Meta AI consent screen ever appears. Same failure with zero app-switching during the flow (we checked that variable too). This was a proper Gradle-packaged build, so packaging is now ruled out: the failure is on Meta's side of the handoff regardless of how the APK is built.
3. Meta AI app v292.1.0 shipped while we were testing; we'll update and retest the Connect button, and capture logcat while tapping Connect to hand you the actual error if it still fails.

Happy to provide any logs or the diagnostic screenshots we captured. If anyone on the Meta side can say whether third-party Wearables.startRegistration() on Gen 2 + Meta AI app 292.x is expected to work at all right now, that would save us a lot of guesswork.