Status Update
Comments
ad...@google.com <ad...@google.com>
ad...@google.com <ad...@google.com>
uc...@google.com <uc...@google.com>
ac...@google.com <ac...@google.com>
ar...@google.com <ar...@google.com> #2
Alan, this doesn't seem to be related to native debugging.
From the previous bug mentioned
lb...@gmail.com <lb...@gmail.com> #3
ar...@google.com <ar...@google.com>
rp...@google.com <rp...@google.com> #4
A work-around is proposed in StackOverflow:
lb...@gmail.com <lb...@gmail.com> #5
Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?
lb...@gmail.com <lb...@gmail.com> #6
du...@google.com <du...@google.com> #7
lb...@gmail.com <lb...@gmail.com> #8
lb...@gmail.com <lb...@gmail.com> #9
lb...@gmail.com <lb...@gmail.com> #10
I have resolved the same issue :)
lb...@gmail.com <lb...@gmail.com> #11
lb...@gmail.com <lb...@gmail.com> #13
I think this issue might be related to one or more of these :
1. Multiple windows of the IDE, sometimes also of different versions (stable&canary, for example)
2. Using a tool ScrCpy to mirror the device (really wish the IDE had this built in)
3. Requesting to debug while already debugging and optionally on some breakpoint
4. Project with both Java&Kotlin inside.
5. Project with warning of Kotlin plugin version used by some library (and sadly it doesn't tell me which, and what I can do about it), even though I use the latest.
lb...@gmail.com <lb...@gmail.com> #14
lb...@gmail.com <lb...@gmail.com> #15
lb...@gmail.com <lb...@gmail.com> #16
du...@google.com <du...@google.com> #17
Has this still been happening?
lb...@gmail.com <lb...@gmail.com> #18
I also wonder if it's related to Android version, or what's on the PC.
lb...@gmail.com <lb...@gmail.com> #19
The command to install&run the app is with "-g" parameter (to grant all permissions), and a call to a batch file to grant notification access ( "adb.exe" shell cmd notification allow_listener ... ) via the "Before launch".
IDE info:
Android Studio Bumblebee | 2021.1.1 Patch 2
Build #AI-211.7628.21.2111.8193401, built on February 17, 2022
Runtime version: 11.0.11+9-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 8048M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: GenerateSerialVersionUID (3.0.3), GenerateSerializationHelpers (1.0.6), Show As ... (1.0.3), com.dubreuia (2.2.0), com.github.beansoft.jadx.gui.idea (2021.2.1), com.intellij.marketplace (211.7628.36), String Manipulation (9.4.0), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), com.google.mad-scorecard (1.2), com.ppismerov.ksvu (0.0.1), net.aquadc.mike.plugin (0.21), izhangzhihao.rainbow.brackets (6.21), org.intellij.plugins.markdown (211.7142.37)
lb...@gmail.com <lb...@gmail.com> #20 Restricted
du...@google.com <du...@google.com> #21
Just an update: looking at the idea.log, it seems like Studio doesn't get to the point where it tries to connect the debugger, which is why you're seeing this issue where the app is waiting for the debugger to attach. I still need to see where in the execution path it may cause an early out (?) after launch, but before debugger attaching.
lb...@gmail.com <lb...@gmail.com> #22
I have a clue though of what I did:
The emulator wasn't launched yet. I pressed the debug button so that it would open the emulator, install, run and debug - all together.
After I've noticed it didn't install at all, I've pressed it again.
du...@google.com <du...@google.com> #23
You don't happen to have two instances of Android Studio open, do you? As for pressing it a second time, I'm guessing that resulted in the bug you're seeing?
lb...@gmail.com <lb...@gmail.com> #24
lb...@gmail.com <lb...@gmail.com> #25 Restricted
lb...@gmail.com <lb...@gmail.com> #26
Please fix this forum bug...
du...@google.com <du...@google.com>
du...@google.com <du...@google.com>
jo...@gmail.com <jo...@gmail.com> #27
Does google know how frustrating this is and makes me wanna throw the phone out the window.
Please focus some energy on this!
Many thanks
Build #AI-221.6008.13.2211.9477386, built on January 11, 2023
sa...@google.com <sa...@google.com> #28
We are aware of this issue and are working on addressing it. Switching from ddmlib
to adblib
in next Android Studio will help. We also have more improvement in the pipeline (like a synchronization mechanism so Android Studio can detect when the app is waiting for the debugger).
el...@gmail.com <el...@gmail.com> #29
lb...@gmail.com <lb...@gmail.com> #30
It might be related to app removal while it's being debugged with a breakpoint.
Attached bug report file from there.
sa...@google.com <sa...@google.com> #31
Could it be that "something" is making debug app persistent via am set-debug-app --persistent PKG
?
Does the problem goes away if you run:
adb shell am clear-debug-app
?
lb...@gmail.com <lb...@gmail.com> #32
I think I restarted the emulator.
du...@google.com <du...@google.com>
sa...@google.com <sa...@google.com> #33
Can you enable adb traces so help us see better was is happening with adb server
. You need to set the env variable ADB_TRACE=all
. Then the log location differ based on your OS. Mac/Linux have it in /tmp/adb<PID.log
or C:\Users\<uid>\AppData\Local\Temp>
.
jc...@gmail.com <jc...@gmail.com> #34
ai...@thisisaim.com <ai...@thisisaim.com> #35
sa...@google.com <sa...@google.com> #36
The reason you may be stuck on this "Waiting for Debugger" is that Studio is unable to match the pid with a package name. If you open the "Device Explorer" and look at the Processes, you should see unidentified processes in red. If you see it, that would get us on a direction to explain the issue (see attachment).
The other thing, is that we asked for adb traced in
je...@gmail.com <je...@gmail.com> #37
Android Studio Ladybug Feature Drop | 2024.2.2
Build #AI-242.23726.103.2422.12816248, built on December 17, 2024
Runtime version: 21.0.4+-12508038-b607.1 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 5120M
Cores: 8
Registry:
ide.instant.shutdown=false
ide.experimental.ui=true
i18n.locale=
Emulator 35.3.11
I notice that it happens when the package installation takes more than 300ms more or less.
lb...@gmail.com <lb...@gmail.com> #38
Google, please check its files and don't remove them till it's fixed.
Description
It happened to me yesterday, on my Pixel 4 Android R.
I had to restart the phone to make it stop.
Android Studio 4.1.1
Build #AI-201.8743.12.41.6953283, built on November 5, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1970M
Cores: 12
Registry: ide.new.welcome.screen.force=true, external.system.auto.import.disabled=true, debugger.watches.in.variables=false
Non-Bundled Plugins: GLSL, String Manipulation, com.dubreuia, org.jetbrains.kotlin