Oculus quest 2 developer mode not working properly

[PLX_T]

Hello,

Since yesterday 15:30 (AMS time) The developer hub app stopped working properly. I've done a total of 3 factory resets. I reinstalled all my accounts. Reinstalled every app on my computer for developing for the oculus. But the problem persists.

The problem is: I connect the oculus through the usb cable to the computer. The hub detects it as usual. But 6 seconds into the future and it kicks the device right of the hub. It tells me: Device detected but unauthorized. Please put on your headset to confirm the USB Debugging dialog. Funny thing is, I allowed this already. I have to restart the device to see this window pop up again. It's on always allow for this computer. But the problem still persists. It kicks my device after exactly 6 seconds and I get the same message, over and over again. Lovely problem. Working already for 6 hours to resolve this problem, but can't seem to find anyone on any forum with the same problem. 

I haven't found a work around so if someone finds a solution or knows what is wrong please let me know. 

Just want to add that this is one of the worst devices I have worked with. Can't seem to get this device to work stable for development. Mark fix your company 

[Joey-Karate]

I'm having the exact same issue and can't seem to find a fix so far. It may be worth noting that I also clicked "always allow for this computer" and it seemed to happen after this was selected.

UPDATE: So it turns out that I only have the issue when I have Build Settings > Android open in Unity, as soon as I close Unity and reconnect the cable, it connects and stays connected in the ODH. I suspect that the two ADB consoles are clashing in some way to cause this but I'm unsure. As long as you don't have the two open at the same time, they both run fine. If somebody could point me in the direction of a bug report, that would be great.

FIX: It is (at least in my case) an ADB conflict issue. Set your ADB path in the Oculus Developer Hub > Settings and change path to the version installed by Unity, typically in "C:\Program Files\Unity\Hub\Editor\2020.3.27f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools" and restart ODH and after this ODH and Unity should share the same ADB connection. I don't believe it's a bug, just lack of information.

I am working on Windows 10 with Unit 2020.3 and with an Oculus Quest 2 running v37 - System version 22310100587300000

[MetaQuestSupport]

Hello all! We see you're experiencing some issues with the developer hub 🤔. While we may not be able to provide support for this issue in particular, we are more than happy to point you in the right direction to get the help you need! Please visit the developer support site here to see FAQs, and to get in touch with agents who can help. 😊👍  

[Val_Tine]

Hi! Was spendet a lot of time but i fixed it! Maybe it don't helping you, but i hope...
I'm only changed cable and nothing kick me from developer Hub and exceptions in Unity was gone.

[harjeetkeitarou]

Hey everyone, 

Found the fix that worked for me:

Disconnect cable from Quest

Turn off Developer Mode in the Oculus App

Restart the Quest

After it reboots and you are connected reenable Dev Mode

Plug-in cable and look in the headset to see if you can authorize it.

The issue was that I must have dismissed the initial authorization screen, and it never came up again. This fixed it.

[tong_chentong]

It worked for me！ Thx so much