Unity can no longer see my Meta Quest 3 Headset

Unity Engine
, ,
1

I’ve got a couple of VR projects I’ve been working on in Unity (6000.0.50f1) and both have been working fine, I could hit Build and Run and I see the results in my Quest 3 headset which is connected by USB.

Today I hit that button and I am told Unity can’t find any Android devices. I get this message -

Make sure your device is plugged in.
If you are sure that the device is attached then it might be USB driver issue, for details please check ‘Android environment setup’ section in Unity manual.

  • I have clicked the Notification to enable USB in the headset.
  • I can see the Quest 3 in Windows Explorer and access its file structure.
  • I can access my Windows Desktop remotely via the Quest - it’s definitley connected!
  • Developer mode is still active and has been turned on and off to check. This has been done on the App and the headset itself.
  • I can still use all my side-loaded apps stored locally on the headset.
  • I have reinstalled the adb driver in Windows.
  • I have updated all Unity Packages.
  • I have updated Unity to 6000.058f2 LTS.

Is there anything else I should be looking at as I’m utterly stumped? I assume an update to the headset has broken something that Unity relies on as everything else still works, but I have no idea what to do about it.

2

so running this on commandline, does show the device too?

adb devices

tried different usb ports, switched cable?

3

No, it doesn’t show under that command line.

Changing ports/cable makes no difference.

4

some other things to try:

  • check if the headset is logged in with correct account, same with the meta desktop app
  • from sdk manager, check that these are installed: google usb, platform tools for that version **i dont know if the sdk manager gui is available with the unity installed sdk..
  • disable airlink (but its probably off already, since using usb)

i guess if nothing else comes up, could try factory reset.. (or another headset or in another pc)

5

Thanks, I only have one account. Everything else is in place. Airlink is off.

I’ve since found that SideQuest won’t connect either, my connection status there passes all checks except for Device Authorisation.

I’ve tried deleting my Android folder on Windows.

6

if “adb devices” shows “..unauthorized”,
then on regular android devices,
switching the connection mode usually helps (to get that accept connection prompt appear).. not sure how that happens in Quest.

just out of interest, could try different windows account too, if same issue.

this can also close the adb server, but im sure you have rebooted pc already.

adb kill-server

and if nothing works,
could also try cloning project and downgrading or testing in new empty empty project, if that builds to device.. (but probably not, if cannot even see the device)

i dont know if Quest has some setting to reset those authorisation dialogs..

7

Absolutlely no idea what’s happened here but it’s started working again!

I just reconnected (again) and it asked me to authorise a specific device code. I did and said to always allow the device and it worked. No idea what triggered that to happen, but it has now allowed me to connect and sync a build. SideQuest worked too.

Thanks for helping.