Bug P3
Status Update
Comments
uc...@google.com <uc...@google.com>
po...@heb.com <po...@heb.com> #2
Steps to reproduce - when profiler is first open and automatically attaches to already running device the issue occurs.
When the device detached with profiler running and manually reconnected - it works as expected.
When the device detached with profiler running and manually reconnected - it works as expected.
yi...@google.com <yi...@google.com>
sh...@google.com <sh...@google.com> #3
- Can you elaborate a bit on the repro steps in
? What do you mean by "automatically attaches to already running device"? Maybe attaching to a running process?comment #2 - Can you get another screenshot with more context, like the one I'm attaching? I'm especially interested in whether the green bar at the top is present (they represent Activity or Fragment).
- Is the expected network traffic happening immediately after the profiler session starts? During the profiler's setup period, it may miss some network traffic.
po...@heb.com <po...@heb.com> #4
Hi,
Yes, attaching to the running process.
Attaching a bigger screenshot.
I tried with network traffic that starts immediately and also waiting and retrying.
The solution is to press stop button to end the session and then press + button to attach to the same process again and then the profiler works as expected.
Yes, attaching to the running process.
Attaching a bigger screenshot.
I tried with network traffic that starts immediately and also waiting and retrying.
The solution is to press stop button to end the session and then press + button to attach to the same process again and then the profiler works as expected.
[Deleted User] <[Deleted User]> #5
Same here. I'm using retrofit which in turn is using okhttp. Thanks for the stopping and restarting trick btw.
La...@ca-ts.fr <La...@ca-ts.fr> #6
I've the same problem. Sometimes you have to attach several times before it works.
My context :
Windows 10 Entreprise x64
Android Studio 4.1.2
Launching app with "Debug" button
My context :
Windows 10 Entreprise x64
Android Studio 4.1.2
Launching app with "Debug" button
li...@xibis.com <li...@xibis.com> #7
Same problem for me, makes it difficult to inspect traffic occurring on app launch
da...@gmail.com <da...@gmail.com> #8
Comment has been deleted.
al...@gmail.com <al...@gmail.com> #9
Comment has been deleted.
Description
Studio Build:
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 24, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.6
GC: ParNew, ConcurrentMarkSweep
Memory: 4012M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: Statistic, org.jetbrains.kotlin, com.google.services.firebase, wu.seal.tool.jsontokotlin
Version of Gradle:
classpath 'com.android.tools.build:gradle:4.0.1'
classpath "com.newrelic.agent.android:agent-gradle-plugin:5.27.0"
Version of Java:
compileOptions {
targetCompatibility 1.8
sourceCompatibility 1.8
}
OS:
Android 11
Steps to Reproduce:
1. Make network call
2. Check profiler