iOS app stuck on "waitingForDevice" - Developer Mode enabled, all requirements met

[thegilbertchan]

Issue Summary

My iOS app is stuck on waitingForDevice state when trying to connect to Ray-Ban Meta glasses, even though all documented requirements are met. The Mock Device Kit works perfectly, but real glasses are never detected.

Environment

• iOS Device: iPhone 14 Pro
• iOS Version: Latest
• Xcode: Latest
• Meta AI App Version: v251.0.0.58.166 (above v247 requirement)
• Glasses: Ray-Ban Meta Gen 1
• Glasses Firmware: v20+
• SDK Version: Latest from Swift Package Manager

Setup Completed

• ✅ Developer Mode enabled in Meta AI app (tapped version 5 times)
• ✅ Developer Mode enabled on glasses
• ✅ Glasses connected and working in Meta AI app
• ✅ Project registered in Wearables Developer Center
• ✅ iOS Bundle ID configured: Gil-Chan.Meta-Companion
• ✅ Universal Link configured
• ✅ Version 1.0.0 created and assigned to Beta release channel
• ✅ Test user (myself) invited and accepted
• ✅ Camera permission rationale added
• ✅ All Info.plist permissions configured (Bluetooth, Camera, Microphone)

Code

Using StreamSession with AutoDeviceSelector:

let wearables = Wearables.shared
let deviceSelector = AutoDeviceSelector(wearables: wearables)
let config = StreamSessionConfig(videoCodec: .raw, resolution: .low, frameRate: 15)
let session = StreamSession(streamSessionConfig: config, deviceSelector: deviceSelector)
try await session.start()
// State is always: waitingForDevice

Logs

Wearables.configure() succeeded
Got Wearables.shared: Optional(MWDATCore.WearablesImpl)
Creating AutoDeviceSelector...
session.start() completed successfully
Current session state after start: waitingForDevice
nw_resolver_start_query_timer_block_invoke [C1.1.1] Query fired: did not receive all answers in time for api2.ar.meta.com:443

What I've Tried

1. Full restart of iPhone, Meta AI app, and my app
2. Tested on both WiFi and mobile data (no VPN)
3. Removed MWDAT Info.plist config (docs say not needed for Developer Mode)
4. Added MWDAT Info.plist config with MetaAppID and AppLinkURLScheme
5. Verified glasses are actively connected in Meta AI app
6. Mock Device Kit works perfectly - confirms SDK integration is correct

Questions

1. Is Associated Domains / Universal Links required for the authorization handoff? (I'm using a free Apple Developer account which doesn't support Associated Domains)
2. Is there additional configuration needed in the Meta AI app beyond enabling Developer Mode?
3. Should the app appear in "App Connections" in Meta AI? I don't see that option.
4. The api2.ar.meta.com timeout suggests authentication issues - is there a way to debug this?

Any guidance would be greatly appreciated!

[metadavithom]

Hi @thegilbertchan!

It's not certain, but I suspect as the app isn't appearing in the "App Connections" in Meta AI, then it is not being successfully registered. When your app registers (and gets added to the connected apps in the MetaAI app), your app should call to MetaAI, the user will confirm they wish to connect, then the MetaAI app will call back to your app with the result.

In order for that to work:

1. You need either to be logged in as a test user who has has the build published in Wearables Developer Center, or have developer mode turned on. it's easiest to test with developer mode first as you need less setup.
2. You will need to ensure your app is configured as a known URL endpoint and tell us that endpoint using the MWDAT section in the plist.

You can see the steps covered here in more detail: https://wearables.developer.meta.com/docs/build-overview#integration-lifecycle, and for iOS here: https://wearables.developer.meta.com/docs/build-integration-ios

Hope that helps! I'd also suggest you get our CameraAccess sample working first, and that will let you can see the correct flow and steps, and see what you're application isn't doing in comparison.

[thegilbertchan]

Thanks @metadavithom and @mathars for the help!

We figured it out. The issue was trying to connect/stream before registration was complete.

The Problem:
We were calling session.start() before the app had fully registered with Meta AI, which left us stuck in waitingForDevice.

The Fix:
Complete the registration flow FIRST, then connect:

1. Call wearables.startRegistration()
2. Wait for registration to complete (user approves in Meta AI app)
3. Monitor registrationStateStream() for .registered state
4. Only THEN start the stream session

  // Wait for registration to complete first
  for await state in wearables.registrationStateStream() {
      if state == .registered {
          // NOW safe to start streaming
          await session.start()
      }
  }

The app needs to appear in "App Connections" in the Meta AI app before you can access the glasses camera. Trying to stream before that will just hang on waitingForDevice.

Thanks again!

[ColinHu07]

Hey @thegilbertchan, did you ever to get the sample CameraAccess app to work or was this just for your own application that you made? If so, do you know what the fixes would be for that? I tried the fixes you just said and fed it into Cursor's Opus 4.5 and that still didn't work either (since I presume this is tailored for your app specifically and not the sample one). Any help would be amazing! Thanks!

[metadavithom]

@thegilbertchan Glad that you got it working!

[mathars]

Hi. can you confirm if you got the sample app from meta working? If yes this is my suggestion.

Use an ide like cursor and import your project and the sample meta project into the workspace. From there tell opus 4.5 in agent mode that you have a sample working project and to get your working. The AI agent will fix it for you. That is how I got my project working.