New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 917128 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 620034



Sign in to add a comment

Android Studio cannot debug _all target

Project Member Reported by dewittj@chromium.org, Dec 20

Issue description

Android studio 3.4 canary 8

If I follow the default instructions in https://chromium.googlesource.com/chromium/src/+/HEAD/docs/android_studio.md then I am unable to debug remote targets.

If I use generate_gradle.py with a specific APK target I'm able to debug.
 
Can you clarify what debug remote targets means? Attaching to a process on the phone?
I can't attach a debugger to a phone or emulator.  It doesn't recognize the APK so it doesn't show the processes in the chooser window. (see attached)

Also, the Edit Configurations dialog has an error which may be related (see attached).


Selection_035.jpg
156 KB View Download
Run-Debug Configurations_036.jpg
179 KB View Download
Cc: wnwen@chromium.org
Labels: DevX
Owner: ----
Status: Available (was: Untriaged)
Hmm... this might be related to using _all rather than passing --target with the specific apk target.

If you figure out a good solution, feel free to take this bug.
I've found that by passing --target, it allows me to attach to processes.

Example: build/android/gradle/generate_gradle.py --canary --target //chrome/android:chrome_public_apk
Blocking: 620034
Status: Untriaged (was: Available)
Available, but no owner or component? Please find a component, as no one will ever find this without one.
Status: Available (was: Untriaged)

Sign in to add a comment