Troubleshooting ADB Unauthorized Device Errors in Android Studio

Troubleshooting ADB Unauthorized Device Errors in Android Studio

22 April 2024 Stephan Petzl Leave a comment Tech-Help

When working with Android Studio and trying to debug an application on a physical device, developers might occasionally encounter an ADB error indicating that the device is unauthorized. This can prevent the device from displaying any Logcat output for the app in question. Understanding how to resolve this issue is essential for maintaining a smooth development workflow.

Understanding the Unauthorized Device Error

The error message typically looks like this:

PropertyFetcher: AdbCommandRejectedException getting properties for device XXXXXXX: device unauthorized. Please check the confirmation dialog on your device.

This error suggests that the device connected to your development machine has not been authorized for USB debugging with the current ADB environment. This authorization is a security measure to prevent unauthorized devices from accessing your application’s data during development.

Steps to Resolve the Unauthorized Device Error

Here are the steps you can take to address this issue:

  1. On your device, open the Developer Options.
  2. Scroll to USB debugging and toggle it off and then back on.
  3. Below USB debugging, find and tap on Revoke USB debugging authorizations. This will clear all remembered authorizations.
  4. Disconnect your device from the PC.
  5. On your development machine, open a terminal or command prompt and execute the following commands:
    adb kill-server
    adb start-server
  6. Reconnect your device to the PC via USB.
  7. A dialog should appear on your device asking you to allow USB debugging. Make sure to check the “Always allow from this computer” option and then tap OK.

If the above steps do not resolve the issue, try changing the USB connection mode to Media or another mode different from the current one before reconnecting your device.

Additional Tips

If you’re still experiencing troubles, consider the following:

  • Check for a faulty USB cable. A bad cable can cause intermittent connections, which might lead to authorization errors.
  • Ensure that ADB integration is enabled in your IDE if applicable (e.g., Android Studio).
  • Try using a different USB port on your development machine.

How Repeato Can Help

In the context of mobile app development and testing, issues like device authorization are common. While the steps outlined above can help resolve such issues, having a robust testing framework like Repeato can further streamline your testing process. Repeato is a no-code test automation tool that supports iOS and Android platforms. It can create, run, and maintain automated tests for your apps without the need to delve into complex ADB commands or device authorization processes.

Moreover, Repeato is designed to work seamlessly with various app frameworks, including React Native, Flutter, and Unity. Its integration with ADB allows you to execute ADB commands through script steps, making it a versatile tool for both development and testing teams. By leveraging Repeato’s computer vision and AI capabilities, you can ensure that your tests are fast to edit and run, providing you with reliable results and saving valuable time.


Resolving ADB unauthorized device errors is crucial for a productive Android development environment. By following the steps provided, developers can quickly troubleshoot and fix these issues. For a more comprehensive testing solution, consider incorporating Repeato into your workflow for efficient, no-code test automation that covers a wide range of frameworks and platforms.

Like this article? there’s more where that came from!