Skip to main content
New Participant
October 3, 2025
Question

Developer Mode Won't Authorise on Meta Quest 3?

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 have clicked the Notification to enable USB in the headset.
  • I can see the Quest 3 in Windows Explorer and access its file structure.
  • 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. Running 'adb.exe devices' lists nothing.
  • I have updated all Unity Packages.
  • I have updated Unity to 6000.058f2 LTS.
  • No amount of reboots to either device helps.

I have since found that SideQuest won't connect either, my connection status on that software passes all checks (including Dev Mode Enabled and ADB Detected) except for Device Authorisation. 

I have deleted my .android folder on Windows to no effect.

Short of a factory reset what are my options here??

2 replies

jtriveri
Honored Contributor
October 3, 2025

Unlikely, but the cable you use could be bad. Have you tried using a different cable? It would at least rule out that issue too.

EDIT: nevermind, you mentioned that file access still worked lol 

jami3rezAuthor
New Participant
October 3, 2025

Don't know why it triggered but I suddenly started getting a popup in the headset acking me to authorise, giving a specific app number. I said yes and to always allow this system and it's fine now.

I've already done this before about a year ago and I've no idea why it needed doing again or why it didn't just ask me to do this in the first place!