Best IT Recipes

Android Studio - ADB error - "... the device is unauthorized. Check the confirmation dialog on your device."

So, I started getting errors in my ADB logs, which I think make my device now display any logcat output for my application. I get all logcat output except one from the application 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.
+102
android android-studio adb android-logcat logcat
Sep 27 '14 at 22:37
source share
16 answers

you missed the “Fingerprint Certificate Authorization” dialog box on your phone, when you connected it, try changing the USB mode to Media or another one different from what you have, and then reconnecting the device or go to “Developer options →” Cancel USB debugging. " and reconnect, look at the dialog box and click "accept", which should solve your problems.

If this does not work, set your ANDROID_SDK_HOME again, and then:

  1. Disconnect device

  2. To run:

     adb kill-server adb start-server

  3. Connect device

+183
Sep 28 '14 at 0:29
source share

I got the same problem.

In order for your Android device to expect the correct fingerprint from the system (for example, after switching the Android SDK settings → on another adb server!), Do the following (in fact, this did the magic for me):

  • disconnect your android device.
  • revoke USB debugging authorization in Android Developer Options
  • connect your device. You can accept the print again.
+27
May 03 '15 at 12:22
source share

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

I ran into the same problem. You may notice that "adb integration" has been disabled. Enable it in your IDE (Tools | Android)

+9
Jan 21 '15 at 1:17
source share

1) Go to "Phone Settings"> "Developer Options"> "Cancel USB Debugging."

2) Disable USB debugging and restart again.

This will work definitely, in my case it worked.

+8
May 04 '17 at
source share

The solution to this was to simply change the USB cable by enabling ADB integration through

Tools> Android> Enable ADB Integration.

+3
Jun 12 '15 at 14:03
source share

This happened to me because I turned on debug debug earlier on another computer. Thus, in order to work on the second computer, I had to turn off usb debugging and turn it back on when connected to the second PC, and it worked.

+3
Mar 12 '16 at 20:00
source share

In my case, it was literally a bad USB cable. Apparently, this was right at the edge - adb logcat would work, but in about half the cases I would get this error when trying to push the application to the device.

Another cable changed, and everything was in order. The old cable was too slow to charge, so I should have suspected it before ...

+1
May 23 '15 at 23:44
source share

Delete debug permissions on the device by connecting a cell phone, then return them and ask if you want to allow the PC to have debug, accept and ready permissions: D

+1
Jan 13 '17 at 18:29
source share

The following are the commands for an Ubuntu user to authorize devices after enabling the developer option.

sudo ~/Android/Sdk/platform-tools/adb kill-server

sudo ~/Android/Sdk/platform-tools/adb start-server

On the device:

  • Developer option activated
  • USB debugging verified

Connect your device now and you only have to accept the request on your phone.

+1
Apr 25 '19 at 10:08
source share

I had the same problem when debugging through wlan. I could run the application from Android Studio, but could not get any messages in logcat.

I installed it by connecting the device to the computer via a USB cable, running the application once and everything worked. Then I disconnected the USB cable and again tried debugging via wlan, and everything worked again.

0
Dec 10 '14 at 10:59
source share

I also have such a message. In my case, I changed my developer's environment to another laptop, and my device is the release of Samsung Galaxy Note 2014. My OS is Windows 7

My galaxy note state is listed below:

  • developer option enabled
  • USB debugging is debugged

The error message was "Unauthorized device. Please check ..."

In general, the default installation location for Android was C:/Users/Your_login_name/.android , after which I copied and pasted all the files into the ".android" folder in the new settings folder for the PC.

After that, the problem disappeared.

I think the problem was adbkey inconsistent. Also, I didn't have any menu name like revoke adb authorization .

0
Sep 11 '15 at 3:01
source share

It seems strange a complicated step and restarting the solution steps ... The first time I connected an Android device to Ubuntu (15.10), I have Connect as: media or camera settings, and in my Android studio the device status was unauthorized. Only after I selected one of the options that I received on the Android device, the PC authorization option. When you give the correct permissions in Android, the status of the device will change to online in Android Studio. Greetings

0
Nov 23 '15 at 3:53 on
source share

It may help - Just download and install the Android SDK version (same as your version of the Android mobile), then launch.

0
Mar 24 '17 at 15:05
source share

Simple! Your phone should only have an appointment request.

0
Jan 01 '18 at 10:32
source share

In my case, the problem was the permissions. I use Ubuntu 19.04 When launching Android Studio as root , my phone will ask for permission to access. But with a regular user this will not work.

So the problem was that adb did not have enough rights. I made my user the owner of the Android folder in the home directory.

sudo chown -R orkhan ~/Android

0
Jun 15 '19 at 15:15
source share
  1. Download platform-tools-latest-linux.zip .

  2. To run:

     unzip platfo*.zip cd plat* ./adb devices / ./adb usb / etc
0
Jun 18 '19 at 13:37
source share


More articles:


All Articles