Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android Studio - ADB Error - "...device unauthorized. Please check the confirmation dialog on your device."

People also ask

How do I authorize my adb device?

The location differs based on the Android version you're running. Under Developer Options, turn off USB Debugging. Under the USB debugging switch, there will be an option called 'Revoke USB debugging authorizations'. Tap it and for good measure, restart your phone.

How do I authorize a device for adb on a Mac?

Reconnect the device to the Mac/MacBook Open a command window and enter „./adb devices„. Watch the device's screen for any Authorization message and allow the connection. The device should now show as „device“.


you have missed the Fingerprint Certificate Authorization dialog in your phone when you connected it, try to change the USB mode to Media, or another different than the one you have in and then reconnect your device, or go to Developer Options -> Revoke USB Debugging and reconnect, watch for the dialog and click on accept, that should solve your problems.

If that doesn't work, set your ANDROID_SDK_HOME again, and then:

  1. Unplug device
  2. Run:

    adb kill-server 
    adb start-server
    
  3. Plug in device


I experienced the same issue.

To ensure that your Android Device is expecting the correct fingerprint from the system (e.g. after switching Android SDK installations -> different adb server running!), do the following (actually, this did the magic for me):

  • unplug your Android Device
  • revoke USB debugging authorizations in Android Developer Options
  • plug your Device. You can accept the fingerprint once more.

Please check this. https://code.google.com/p/android/issues/detail?id=82850

I faced the same issue. Could notice that the "adb integration" was disabled. Please enable it at your IDE (Tools | Android)


1) Go to Phone Setting > Developer options > Revoke USB debugging.

2) Turn off USB debugging and Restart Again.

It will work definitely, in my case it worked.


This happened to me because I enabled usb debug previously on another pc. So to mke it work on a second pc I had to disable usb debugging and re-enable it while connected to the second pc and it worked.