Not Able To Debug App In Android Studio

AndroidDebuggingAdbAndroid Studio

Android Problem Overview

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:

screenshot

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.

Android Solutions

Solution 1 - Android

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

Solution 2 - Android

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.

Click here to debug

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>

Solution 3 - Android

Another thing to be careful of (I did this so I know, duh). Be sure not to enable Proguard for debug!

Solution 4 - Android

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.

Solution 5 - Android

    <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"

Debug Mode

In Android Studio, go to BUILD -> Select Build Variant

Now try debugging. Thanks

Solution 6 - Android

This worked for me:

  1. Close Android Studio.

  2. Open the shell, and write:

    adb kill-server

    adb start-server

Solution 7 - Android

If your Application used to be debuggable, and suddenly it's no more debuggable.Here is my solution

  1. disable and enable USB debug switch in your phone.
  2. Uninstall your application.
  3. click Run in Android Studio.

Solution 8 - Android

Make sure you have enabled the ADB integration.

In Menu: Tools -> Android -> Enable ADB integration (v1.0)

Solution 9 - Android

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.

Solution 10 - Android

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:

  1. Uninstall application from device.
  2. Clean Project. "Build -> Clean Project."
  3. Rebuild and install.

Solution 11 - Android

"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.
enter image description here

Solution 12 - Android

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 https://stackoverflow.com/questions/39855656/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 https://stackoverflow.com/questions/36785014/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>

Solution 13 - Android

In my case, i forgot minifyEnabled=true and shrinkResources=true in my debug buildType. I change these values to false, it's worked again!

enter image description here

Solution 14 - Android

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...

enter image description here

Solution 15 - Android

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

Solution 16 - Android

Also make sure you're not using other applications that might be using ADB too, like Eclipse for example.

Solution 17 - Android

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

Solution 18 - Android

I did clean build using below command.. Surprisingly worked.

> sh gradlew clean build

Hopefully someone get help!

Solution 19 - Android

Restart the adb server, from android studio: Tools -> "Troubleshhot Device Connection"

Solution 20 - Android

Be sure to enable developer mode and USB debugging on the device or emulator. (Easy to forget when setting up a new one.)

Solution 21 - Android

You also should have Tools->Android->Enable ADB Integration active.

Solution 22 - Android

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'
        }

Solution 23 - Android

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':enter image description here

Solution 24 - Android

This worked for me in Android Studio 3.6.3

> Settings -> Build, Execution, Deployment -> Debugger -> Android Debug > Bridge -> Enable 'Use libs backend'

enter image description here

Solution 25 - Android

This solved my problem. Uninstall app from device and run it again via Android studio.

Solution 26 - Android

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

Solution 27 - Android

<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.

enter image description here

Solution 28 - Android

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.

Solution 29 - Android

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"

enter image description here

In case this menu is not available in your IDE you can do the following.

  1. Double click your shift button and you should see a search window popping.
  2. Type "Build Variants" as shown below

enter image description here 3. Now change your build to debug from QA or Release.

Solution 30 - Android

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. enter image description here

Solution 31 - Android

Here's a little oops that may catch some: It's pretty easy to accidentally have a filter typed in for the logcat output window (the text box with the magnifying glass) and forget about it. That which will potentially filter out all output and make it look like nothing is there.

Solution 32 - Android

In my case I had the same problem because I try to debug signed apk. In my gradle config I made differents build variants, and try to debug release build with production keystore.jks

Solution 33 - Android

What worked for me in Android Studio 3.2.1

Was:

RUN -> Attach debugger to Android Process --> com.my app

Solution 34 - Android

enter image description here

My problem was:

  1. i was using other debug app apart from my current project in AS.
  2. when i click on 'attach to debugger' it was saying "there is no process with com.xyz.abc.appname"

This helped me: just after 'make project/build' button, there is 'select run/debug configuration' > go to 'Edit configuration' The configuration is shown in the image. then my debugger started working.

Solution 35 - Android

Sync your project with Gradle files and that shall help.

Solution 36 - Android

I had same problem and I tried almost all kinds of solutions via Google. But I couldn't solve it. Finally, I found the solution. This is Android Studio Bug.

Do not click Run (Alt + F10) — just click Debug (Shift + F9).

Then Android Studio will show you the Warnning Message with ADB, Then Just click "OK".

You can see log in logcat console. And Packages will be shown on DDMS(Devices).

Categories
Recommended Android Solutions
Recommended Debugging Solutions
Recommended Adb Solutions
Recommended Android Studio Solutions

Previous Solution:

Check If Activity Has Been Called for Result

AndroidAndroid ActivityStartactivityforresult

Next Solution:

Extract code country from phone number [libphonenumber]

AndroidLibphonenumber

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAndy Roy D.View Question on Stackoverflow
Solution 1 - AndroidPrathamesh GujarView Answer on Stackoverflow
Solution 2 - Androidfree3domView Answer on Stackoverflow
Solution 3 - AndroidJohn SmithView Answer on Stackoverflow
Solution 4 - AndroidAdam JohnsView Answer on Stackoverflow
Solution 5 - AndroiditzoView Answer on Stackoverflow
Solution 6 - AndroidlimlimView Answer on Stackoverflow
Solution 7 - AndroidMiao1007View Answer on Stackoverflow
Solution 8 - AndroidmyfknollView Answer on Stackoverflow
Solution 9 - AndroidHarriView Answer on Stackoverflow
Solution 10 - AndroidKyleTView Answer on Stackoverflow
Solution 11 - Androiduser1700099View Answer on Stackoverflow
Solution 12 - AndroidCoolMindView Answer on Stackoverflow
Solution 13 - AndroidMeteView Answer on Stackoverflow
Solution 14 - AndroidlongiView Answer on Stackoverflow
Solution 15 - AndroidSanta TecladoView Answer on Stackoverflow
Solution 16 - AndroidPedro OliveiraView Answer on Stackoverflow
Solution 17 - AndroidAmir ZiaratiView Answer on Stackoverflow
Solution 18 - AndroidshaibanView Answer on Stackoverflow
Solution 19 - AndroidWebdmaView Answer on Stackoverflow
Solution 20 - AndroidKen RootView Answer on Stackoverflow
Solution 21 - AndroidNSKView Answer on Stackoverflow
Solution 22 - AndroidSachin K PissayView Answer on Stackoverflow
Solution 23 - AndroidBajrang HuddaView Answer on Stackoverflow
Solution 24 - AndroidPavel KataykinView Answer on Stackoverflow
Solution 25 - AndroidAhmad BehzadiView Answer on Stackoverflow
Solution 26 - AndroidNaveed AhmadView Answer on Stackoverflow
Solution 27 - AndroidPrakashView Answer on Stackoverflow
Solution 28 - AndroidvanomartView Answer on Stackoverflow
Solution 29 - AndroidNagaraj AlagusundaramView Answer on Stackoverflow
Solution 30 - AndroidSana EbadiView Answer on Stackoverflow
Solution 31 - AndroidRick GiulyView Answer on Stackoverflow
Solution 32 - AndroidWorieNView Answer on Stackoverflow
Solution 33 - AndroidKevin AmiranoffView Answer on Stackoverflow
Solution 34 - AndroidSurajkumar_cseView Answer on Stackoverflow
Solution 35 - AndroidRaheeView Answer on Stackoverflow
Solution 36 - AndroidGuestView Answer on Stackoverflow