How do I fix "Could not connect to remote process" while trying to debug the application?

Question

I am making a android studio project and I try to debug my application.

Running the application works fine, but when I try to debug it I get this error:

Could not connect to remote process. Aborting debug session.

What can I do to fix the issue?

score 40 · Accepted Answer · answered Dec 28 '18 at 18:39

40

You need to restart the ADB.

kill adb.exe process.

how to restart ADB manually from Android Studio

answered Dec 28 '18 at 18:39

Daniel B.

2,491
2
12
23

2

Killing the adb.exe by hand works for me every time. Manual restart from the studio does not work, when I get this error. – H.A.H. Jun 05 '19 at 08:03
This works for me, but only when it's in use and I have to force kill it. "taskkill /IM adb.exe /F" Which happens when it's in actual use trying to connect. If I stop the debugging session and then kill it, it doesn't work. – LordWabbit Oct 19 '20 at 12:41

score 19 · Answer 2 · answered Aug 02 '21 at 15:59

19

Sometimes this happens when two Android-capable IDEs are opened, e.g. Android Studio and IDEA. Shutdown one of the two (or disable Android plugin in IDEA) helps.

answered Aug 02 '21 at 15:59

Kuzneц

707
4
7

Definitely one of the use cases. When this is happening, no other solutions work. – guness Nov 03 '21 at 13:59

score 17 · Answer 3 · answered Jun 11 '19 at 07:58

17

In My case, For some reason I disabled Instant run and it has changed the Launch value from "Default Activity" to "Nothing" in "Run/Debug configurations". So always it says "Could not connect to remote process. Aborting debug session" and I was not able to debug. I enabled Instant and changed the Launch value from "Nothing" to "Default Activity" in "Run/Debug configurations" and it worked. Hope this will help some one.

(to get Run/Debug configurations, click "app" drop down and click Edit Configurations)

answered Jun 11 '19 at 07:58

nuwancy

361
4
4

This was my problem. Thanks a million @nuwancy – Farrukh Najmi Oct 21 '19 at 19:40
killing the adb.exe was usleese for me , but this work like charm ;) + – Erfan Dec 13 '20 at 09:31
after loosing some hours i find this solution. thanks man. – Shihab Uddin Jul 08 '21 at 09:52
The answer hit my problem :-) Thx! – softburger Nov 18 '22 at 07:52

score 6 · Answer 4 · edited Jun 11 '19 at 09:24

6

Check if you have selected the right Build Variant, usually "release" comes with debuggable false

Example:

 buildTypes {
        release {
            debuggable false
            ....
        }
    }

is not recommendable change release to debuggable true, just change the right variant

   debug {
        debuggable true
        ....
    }

edited Jun 11 '19 at 09:24

Zoe

27,060
21
118
148

answered May 16 '19 at 02:06

Azhagthott

492
5
13

score 6 · Answer 5 · answered Feb 23 '22 at 19:40

6

Verify on AndroidManifest that your LAUNCHER activity has:

android:exported="true"

answered Feb 23 '22 at 19:40

Bhola Bhala

179
2
8

score 5 · Answer 6 · answered Apr 27 '21 at 11:47

5

I try invalidate cache / restart and it's work

answered Apr 27 '21 at 11:47

Vanya Rachel

1,329
1
18
20

score 4 · Answer 7 · answered Jan 13 '20 at 09:41

4

In command line :

adb kill-server && adb start-server

This command will restart ADB

answered Jan 13 '20 at 09:41

Kevin ABRIOUX

16,507
12
93
99

score 3 · Answer 8 · answered Feb 27 '22 at 01:18

3

+1 to Kuzneц's answer.

When Intellij and Android Studio are both open, apparently the Android plugin in Intellij needs to be disabled. This wasn't always the case but it resolve the issue for me.

Mac OSX 12.2.1
IntelliJ 2021.3.1
Android Studio 2021.1.1 Patch 2

answered Feb 27 '22 at 01:18

D Smith

31
2

Thank you, this is the only way that resolves my issue. In my case is Android Studio 2021.1.1 Patch 3, cannot connect to Debugger using AVD Android API 29, – heri.sulis Apr 26 '22 at 14:20

score 2 · Answer 9 · answered Feb 17 '20 at 13:04

By default Android Studio builds the debug version of the application. However, during the publishing phase you may have switched to the release one as the tutorial suggests.

ADB won't be able to attach to the application unless you revert to the debug configuration or you allow to the debug the release one.

If nothing of this works, you may resort in restarting ADB as explianed in How to restart ADB manually from Android Studio

Revert to debug configuration

Choose Build->Select Build Variant
Pick up debug in the second column
Deploy the application again

Allow the release version to be debugged

Select your application node in the tree
Right click and choose Open Module Settings (or hit F4)
Select Build Variants on the left
Choose release on the right
Set debuggable to true
Apply and deploy the application

Keep in mind that your life won't be easy as your application may be optimized and therefore not debugger friendly (e.g. you might not be able to step in certain methods, or view some local variables).

Could you please explain the downvote so that I can improve my answer? — Yennefer, Feb 26 '20 at 06:54

score 1 · Answer 10 · edited Nov 04 '21 at 13:24

1

Restarted the ABD server. First the device had to be connected. Look for the "Assistant" tab in android studio (on the right side it usually is), and press next until you see the option to reset the ABD server.

edited Nov 04 '21 at 13:24

ouflak

2,458
10
44
49

answered Nov 04 '21 at 11:47

Claudio

86
6

score 1 · Answer 11 · answered Nov 26 '21 at 05:34

I did

--->adb kill-server && adb start-server

--->invalidate cache / restart

but not work yet

Waiting for application to come online: com.example.distribution_system | com.example.distribution_system.test

Waiting for application to come online: com.example.distribution_system | com.example.distribution_system.test
    
Waiting for application to come online: com.example.distribution_system | com.example.distribution_system.test
    
Could not connect to remote process. Aborting debug session.

image1:--> [1]: https://i.stack.imgur.com/HZF5D.png

image2:--> [2]: https://i.stack.imgur.com/hrE4a.png

I had the same issue after upgrading android studio to Bumblebee, this solution worked for me as well a teammate, Thanks @Mosen_AB — Ahmed Nezhi, Feb 07 '22 at 10:02

score 0 · Answer 12 · answered Jun 07 '20 at 06:46

0

I got this error message when the phone was connected both via wi-fi (using "adb tcpip 5555" and "adb connect 192.168.0.100:5555" commands) and via a usb cable. Disconnecting the USB cable resolved the issue.

answered Jun 07 '20 at 06:46

Sergey

1,020
11
22

score 0 · Answer 13 · answered Jul 28 '20 at 22:47

0

The other solutions posted here did not help me. I eventually discovered that creating a new simulator instance (tools->AVD Manager->Create virtual device) solved my problem. I was unable to get the previous simulator working again.

answered Jul 28 '20 at 22:47

dacoinminster

3,637
2
18
23

score 0 · Answer 14 · answered Apr 29 '22 at 09:24

0

I followed all the recommendations above, but the problem was solved only after I used the Generate Signed Bundle and selected the desired flavor

answered Apr 29 '22 at 09:24

Сергей Озерный

1

score 0 · Answer 15 · answered Jul 26 '22 at 09:45

For me the problem was a wrong launch flag set in the Run/Debug Configurations. I found out about this by taking the adb command that is executed to launch the app, which can be found in the "Run" tab. The command looks like this:

adb shell am start -n "com.your.package...." -a android.intent.action.MAIN -c android.intent.category.LAUNCHER

By executing the command manually in the terminal, i got an error message which pointed me to the problem.

score 0 · Answer 16 · answered Sep 12 '22 at 10:16

0

All solution didn't fix my issue, If you face it same me try that solution enter link description here

answered Sep 12 '22 at 10:16

Mohamed Mohamed Taha

145
3
8

score 0 · Answer 17 · answered Aug 09 '23 at 02:29

My case
- use Android Studio create a simple android app but no activity
  - current settings: Android Studio->Run->Edit Configuration->General->Launch Options->Launch: Nothing
    - for later used as Xposed plugin, which is no need UI=activity
Error
- first Timed out waiting for process to appear on
- final error: Processes are not found Aborting session
Reason
- for Android app, activity ~= process
  - no activity mean can not debug
Solution
- for me
  - done nothing
    - for no activity android app: can NOT debug
      - activity == UI page ~= proecess, so no activity means no process, cause can not debug
- for others (normal android with activity)
  - change Launch to Default Activity

How do I fix "Could not connect to remote process" while trying to debug the application?

17 Answers17

Linked