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.
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:
- Unplug device
adb kill-server adb start-server
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.
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.
The solution to this was just to change the USB cable, having enabled
ADB Integration via
Enable ADB Integration.
Below are the commands for Ubuntu user to authorise devices once developer option is ON.
sudo ~/Android/Sdk/platform-tools/adb kill-server
sudo ~/Android/Sdk/platform-tools/adb start-server
- Developer option activated
- USB debugging checked
Connect your device now and you must only accept request, on your phone.
In my case, it was literally a bad USB cable. Apparently it was right on the edge – adb logcat would work, but about half the time I would get this error when trying to push an app to the device.
Changed to a different cable, and everything was fine. The old cable was also very slow at charging, so I should have suspected it sooner…
Remove the Debug permissions on the Device, with the cell phone connected, then put them back, and ask if you want to allow the PC to have debug, accept and ready permissions: D
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.
I’ve got the same message too.
In my case, I have changed my dev environment to another notebook pc and my device is samsung galaxy note 2014 edition.
My OS is windows 7
My galaxy note condition listed as following
- developer option activated
- USB debugging checked
The error message was “device unauthorized. Please check the…”
In general, the location of the default android setting was
C:/Users/Your_login_name/.android then I copied and pasted all files in the ‘.android’ folder to my new pc’s setting folder.
After that the problem was gone.
I think the problem was
adbkey file mismatched.
Also, I didn’t have any menu name such as
revoke adb authorization.
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
This might help –
Just Download and install the Android SDK version(same as your mobile’s android version), then run.
Simple! You must only acept request, on your phone.
In my case the problem was about permissions. I use
When running Android Studio in
root user it would prompt my phone about permission requirements. But with normal user it won’t do this.
So the problem was about
adb not having enough permission.
I made my user owner of
Android folder on
sudo chown -R orkhan ~/Android
unzip platfo*.zip cd plat* ./adb devices / ./adb usb / etc
I get this error very often for some reason when doing “ionic cordova run android” and running on an emulator. What works for me is to end the “adb.exe” process and re-run. Sometimes that also doesn’t work and what I do is exit the emulator and in android studio do a “Cold Boot” on the emulator.