14

I have a problem with Android Studio.
Debugger Console says "Failed to connect" and debugging doesn't start.
This problem is occurred in any Android device(include virtual device).
Please give me some ideas to solve this problem.


I tried

  • Invalidate Cashes and Restart Android Studio
  • Uninstall Android Studio and Re-install
  • Clean Project
  • Rebuild Project
  • Refresh Linked C++ Project
  • Re-install LLDB, Android SDK Platform-Tools, and Android SDK Tools


My Environment

  • Android Studio 3.5
  • All SDK Tools are latest version
  • OS:Windows10


in Debugger console:

09/12 15:38:17: Launching 'Unnamed' on Pixel XL API 28.
$ adb shell am start -n "com.yourcompany.prototype3/com.yourcompany.Prototype3" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D
Waiting for application to come online: com.yourcompany.prototype3 | com.yourcompany.prototype3.test
Waiting for application to come online: com.yourcompany.prototype3 | com.yourcompany.prototype3.test
Connecting to com.yourcompany.prototype3
Now Launching Native Debug Session
$ adb shell cat /data/local/tmp/lldb-server | run-as com.yourcompany.prototype3 sh -c 'cat > /data/data/com.yourcompany.prototype3/lldb/bin/lldb-server && chmod 700 /data/data/com.yourcompany.prototype3/lldb/bin/lldb-server'
$ adb shell cat /data/local/tmp/start_lldb_server.sh | run-as com.yourcompany.prototype3 sh -c 'cat > /data/data/com.yourcompany.prototype3/lldb/bin/start_lldb_server.sh && chmod 700 /data/data/com.yourcompany.prototype3/lldb/bin/start_lldb_server.sh'
Starting LLDB server: /data/data/com.yourcompany.prototype3/lldb/bin/start_lldb_server.sh /data/data/com.yourcompany.prototype3/lldb unix-abstract /com.yourcompany.prototype3-0 platform-1568270301152.sock "lldb process:gdb-remote packets"
Failed to connect port

Process finished with exit code 0


in Logcat:

2019-09-12 16:11:30.672 6551-6551/? I/pany.prototype: Not late-enabling -Xcheck:jni (already on)
2019-09-12 16:11:30.700 6551-6551/? W/pany.prototype: Unexpected CPU variant for X86 using defaults: x86
2019-09-12 16:11:30.905 6551-6551/com.yourcompany.prototype3 W/ActivityThread: Application com.yourcompany.prototype3 is waiting for the debugger on port 8100...
2019-09-12 16:11:30.907 6551-6551/com.yourcompany.prototype3 I/System.out: Sending WAIT chunk
nmr
  • 15,900
  • 10
  • 49
  • 62
BakaScript
  • 143
  • 6

4 Answers4

19

It's caused by broken Android SDK Platform-Tools 29.0.3

To solve this issue you should download platform tools 29.0.2 from (mac, win, linux). Extract it and replace platform tools inside Android SDK.

UPD: This issue has been hotfixed with platform-tools 29.0.4: https://issuetracker.google.com/140369526 Now you can update to the latest version, instead of a downgrade.

Evgen Bodunov
  • 3,778
  • 1
  • 26
  • 38
  • 5
    Guess I will think twice next time before clicking update in the pop-up at the bottom right. – Jim Rhodes Sep 12 '19 at 18:46
  • 1
    Android Studio: for those times when hitting your head against a brick wall just isn't painful enough! – CCJ Sep 12 '19 at 21:05
  • Thank you for your idea! I haven't tried this way yet. But many votes tell me that is effective. After trying, I will report whether the problem was solved. – BakaScript Sep 13 '19 at 05:07
  • @BakaScript happy to help. :) – Evgen Bodunov Sep 13 '19 at 07:45
  • For me this happens also on 29.0.2, and it was actually reported to google before 29.0.3. Also since some version I noticed that when I try to attach debugger to native process, AS starts with gradle build which takes some time. – marcinj Sep 13 '19 at 20:47
  • 1
    and now, 29.0.4 was released. I tried this one. it works correctly! – BakaScript Sep 13 '19 at 23:08
1

I also have same bug. No need to do rebuild,clean, restart or uninstall. Just change Run --> Edit Configuration --> Debug Type --> Change to Java. Even for Native build application change to Java. This bug is due to the latest update of lldb server.

Gobzzz
  • 11
  • 1
  • Thank you for your ideas. In your way, debugger starts but can't debug C++ Code. When I set "Native" or "Dual", same bug is occurred. – BakaScript Sep 12 '19 at 11:37
  • After updating the platform tools. its working fine now for me. In auto,Java or native mode. – Gobzzz Sep 20 '19 at 09:48
1

Try set Debugger type to "Java Only"

You can follow this way:

Run -> Edit Configuration -> Android App -> Your app module -> debugger -> set "Java Only" enter image description here

fahrizal89
  • 212
  • 2
  • 11
0

I have the same bug, but my project doesn't have C++ code. I went to Run -> Edit Configurations -> Debug -> Debug type and set it to "Java" instead of "Auto". Maybe if you chose "Native" it will fix the problem for you.

Fyodor Sherstobitov
  • 595
  • 1
  • 4
  • 17
  • 1
    Thank you for your ideas. my project have C++ code. When I set "Native" or "Dual", same bug is occurred. In case of "Java", C++ debugging is not available. – BakaScript Sep 12 '19 at 11:40