Search code examples
androidunity-game-enginevirtual-realityoculusoculusquest

Oculus Quest 2 - Android Device is not responding on Unity on Macbook Pro - Make sure USB debugging has been enabled


I build my first VR app using unity. I am getting the following error when trying to build and run on a connected Oculus Quest 2 device!

Android device is not responding! Make sure USB debugging has been enabled and that the device has authorized this computer. Check your device, in most cases there should be a small icon in the status bar telling you if the USB connection is up.

I have tried many different ways to get this working, I am not able to figure this out, is there anything else I can try? I have listed down things I tried and config I have!

  • I have developer mode ON.
  • When I connect USB to Macbook Pro I do get an option to Allow in oculus quest with the following message and I select "Allow":

Allow Access to data, the connected device will be able to access files on this headset. [Deny] [Allow]

  • I see my Oculus quest device in the "Run Device" dropdown in build settings and have it selected.
  • I also installed Android File Transfer and I do see all folders and files on the quest 2 device.
  • I tried a factory reset and restarting the quest 2 device and my MacBook pro multiple time.
  • App I have built runs fine when I click the play button and also it works when I build for the macOS and run on Macbook pro.

Screen shot for the settings and error File > Build Settings

enter image description here

Thank you!


Solution

  • It is working after I installed the android platform tools.

    1. Install android-platform-tools
    brew install android-platform-tools
    
    1. Reconnect the USB to Oculus Quest 2 device, this time in oculus I got 2 confirmation boxes! One of them has my laptop address and also the checkbox to remember. I selected Allow.

    2. After that File > Build and Run is now working all fine!

    It required to have other updates to the settings but after I installed adb I did get the 2 confirmations in the quest when I connected and now the build and run functionality works all fine!