Android Studio - ADB Error - “…device unauthorized

Question

So I started getting errors in my ADB logs which, I think, are causing my device to now display any logcat output for my app. I am getting all the logcat output except the one from the app itself.

PropertyFetcher: AdbCommandRejectedException getting properties for device 04799057970ed1fc: device offline
PropertyFetcher: AdbCommandRejectedException getting properties for device 03799467970ed5fg: device unauthorized. Please check the confirmation dialog on your device.

Answer 1

Seems strange the intricate cable&restart solution steps ... The first time I've plugged the Android device to my Ubuntu (15.10) I've got Connect as: multimedia or camera options and in my Android Studio the device status was unauthorized. It wasn't until I choose between one of the options that I got in the Android device the PC authorization option. When you give the proper permissions in Android then the device status changed to online in Android Studio. Cheers

Answer 2

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

Answer 3

I had the same problem when debugging over wlan. I could launch the application from Android Studio but couldn't get any messages in logcat.

I fixed it by connecting the device to my pc via USB cable, launched the application once and everything was working. Then I disconnected the USB cable and tried debugging again via wlan and everything was working again.

Answer 4

1. Download platform-tools-latest-linux.zip.

2. Run:

   unzip platfo*.zip
   cd plat*
   ./adb devices / ./adb usb / etc
   

Answer 5

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)

Answer 6

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.