ADB/Developer Mode issues on Meta Quest Developer Hub? Try this!

Hello all! There have been a few bug reports and issues lately surrounding not being able to connect to a device on Meta Quest Developer Hub. Many of these issues can be resolved by simply ensuring that the correct adb is being used universally across the system.

Symptoms of the problem:
- You've completed the 'Set Up New Device' steps on MQDH or enabled developer mode on the Oculus App, but the device does not appear in MQDH's Devices tab.

Diagnosing:
MQDH uses adb for a lot of what it provides to developers, and in order for MQDH to detect the device, the version of adb that MQDH is using must also see the device. This can be checked by opening a console, navigating to the adb install location (This can be seen and/or changed in MQDH settings), and typing `adb devices`.. If there is no device listed there, then the issue may be one or more of:

- The prompt in the headset to allow the computer to access the device was denied
- There is another adb daemon running on the machine that has the device
- The cable used to connect the device to the computer is faulty

Fixing the first and third issues is fairly straightforward. The second may be trickier to run down, but most often what is happening is that a different adb is in use (usually from your game engine or Android SDK install), and in order to get MQDH to see the device, the adb path in MQDH's settings should align with the other adb path that sees the device. Once this is done, restart MQDH and the device should appear. 

Hopefully this helps anyone coming to the forums to troubleshoot this problem!