I am making an app in Android Studio, now trying to debug it through adb. When I click on the word Android and the logo on the bottom bar, logcat comes up and recognizes my device. Then I see this:
What do I need to do to my app to make it "debuggable"?
FYI was developing this app in Eclipse before and adb worked fine.
I solved this issue after doing the following steps:
Go to Tools==>android==>Disable ADB integration and enable it again.
After that, unplug USB from device and plug in again.
Finally press shift + F9
There is a Debug icon on the toolbar. It looks like a little "bug" and is located right next to the Run icon (which looks like a play button). Try launching the application with that.
Edit: The following is deprecated when using Android Studio with Gradle.
There is also a debug flag in the AndroidManifest.xml file. It is located under the application tag, and should be set to "true", as follows:
<application android:debuggable="true"> </application> 
File -> Settings -> Keymap - they are located under Main menu -> Run. See this for more info.
Another thing to be careful of (I did this so I know, duh). Be sure not to enable Proguard for debug!
This worked for me:
Open the shell, and write:
adb kill-server
adb start-server
<application android:debuggable="true"> </application> This no longer works! No need to use debuggable="true" in manifest.
Instead, you should set the Build Variants to "debug"
In Android Studio, go to BUILD -> Select Build Variant
Now try debugging. Thanks
I also randomly had this problem even after debugging many times in Android Studio. One day the debugger just wouldn't attach. I just had to quit Android Studio and reopen it and the debugger started working again.
If your Application used to be debuggable, and suddenly it's no more debuggable.Here is my solution
USB debug switch in your phone.Make sure you have enabled the ADB integration.
In Menu: Tools -> Android -> Enable ADB integration (v1.0)
This occasionally happens to me and I have yet to figure out why. None of the already posted solutions have worked for me. The only thing that works for me is to:
One case where you can be unable to debug an application in Android Studio is when you have the "release" build variant selected. Happened to me - Gradle builds a release version of the app (which is not debuggable) and then Android Studio fails at trying to connect the debugger.
"Attach debugger to Android process" icon shoud be used in case when you set custom "android:process" in your Manifest file.
In my case I should select suitable process and click OK button just after "Wait for debugger" dialog appears.
In my case near any line a red circle appeared with a cross and red line with a message: "No executable code found at line ..." like in Android studio gradle breakpoint No executable code found at line.
A problem appeared after updating of build.gradle. We included Kotlin support, so a number of methods exceeded 64K. Problem lines:
buildTypes { debug { minifyEnabled true Change them to:
buildTypes { debug { minifyEnabled false debuggable true Then sync a gradle with a button "Sync Project with Gradle Files". If after restarting of your application you will get an error: "Error:The number of method references in a .dex file cannot exceed 64K. Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html", then, like in The number of method references in a .dex file cannot exceed 64k API 17 add the following lines to build.gradle:
android { defaultConfig { ... // Enabling multidex support. multiDexEnabled true } ... } dependencies { implementation 'com.android.support:multidex:1.0.2' } UPDATE
According to https://developer.android.com/studio/build/multidex.html do the following to enable multidex support below Android 5.0. Else it won't start in these devices.
Open AndroidManifest and find tag <application>. Near android:name= is a reference to an Application class. Open this class. Extend Application class with MultiDexApplication so:
public class MyApplication extends MultiDexApplication { ... } If no Application class set, write so:
<application android:name="android.support.multidex.MultiDexApplication" > ... </application> In my case, i forgot minifyEnabled=true and shrinkResources=true in my debug buildType. I change these values to false, it's worked again!
Check, if you're app-project is selected in the drop-down menu next to the debug-button. Sometimes Android Studio just resets this selection...
If you enable
<application android:debuggable="true"> </application> In the application manifest.xml make sure you disable it when generating the final signed apk since this can serve as a security loop hole for attackers. Only use it if only one of your applications does not show the logs. However before considering that option try this:
Navigate to tools in the android studio
Tools==>android==>disable adb integration and again enable it I tested all ways and non of them worked !!!
finally had to change the adb port and it worked. first kill adb server like below:
adb kill-server then restart it using another port
adb -P 5038 start-server Restart the adb server, from android studio: Tools -> "Troubleshhot Device Connection"
This worked for me in Android Studio 3.6.3
Settings -> Build, Execution, Deployment -> Debugger -> Android Debug Bridge -> Enable 'Use libs backend'
April 2022 :
all the answers did not help me in android studio 2022, I found my solution, maybe help someone else: I got this error in debug window when I was using breakpoint and debug mode:
Signal: SIGILL (signal SIGILL: illegal instruction) android studio So the solution is:
go to Run> Edit Configuration > Debugger Tab select Java only from debug type. 
Also make sure you're not using other applications that might be using ADB too, like Eclipse for example.
In my case, Had to remove the proguard in debug Build Type by completely clearing the text file proguard-rules.pro and making minifyEnabled false in build.gradle file
debug { debuggable true minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } In my case, I was trying to debug from a QA build. Change the build variant to Debug and it should work.
To change the build variant, click the menu on the left bottom named "Build Variants"
In case this menu is not available in your IDE you can do the following.
3. Now change your build to debug from QA or Release.
Be sure to enable developer mode and USB debugging on the device or emulator. (Easy to forget when setting up a new one.)
You also should have Tools->Android->Enable ADB Integration active.
I did clean build using below command.. Surprisingly worked.
sh gradlew clean build
Hopefully someone get help!
Over the years I have visited this thread many times and there was always a different response that helped me. This time I figure out that it's my USB hub that was preventing debugger to work properly. As strange as it sounds, instead of having a phone connected to my computer via a USB hub, I had to connect it directly to my mac and debugging started to work.
I was able to fix it by going to Run -> Edit Configurations, selecting my project, selecting the Debugger tab, then changing 'Debug type' from 'Auto' to 'Dual':
This solved my problem. Uninstall app from device and run it again via Android studio.
For me, it happened when I used Proguard, so by trying all the solutions I cleaned my project and pressed the debug button on Android Studio and it started debugging
<application android:debuggable="true"> </application> That above code is not longer a solution. You need to enable debugging inside your build.gradle file. If you have different buildTypes make sure you set "debuggable true" in one of the build types. Here is a sample code from one of my projects.
buildTypes { debug { debuggable true } release { debuggable false } } **I have deleted other lines inside the buildTypes which are not relevant to this question from my gradle file here.
Also Make sure you select the correct build variant in your android studio while doing the debugging.
