Obsolete
Status Update
No update yet.
Comments
yo...@gmail.com
My Nexus 6P phone is running 7.0 final.
If I manually use the "attach debugger to Android process" action, then the test recorder will popup.
If I manually use the "attach debugger to Android process" action, then the test recorder will popup.
ja...@google.com
sn...@google.com
Thank you for reporting this issue. I would like to clarify several points:
1) Does this problem happen every time you launch Espresso Test Recorder or only the first time or is it flaky?
2) Does this problem also happen when you try to debug your app (with the same run configuration you use for Test Recorder)?
3) Could you please attach idea.log file after you experience the reported issue (Help | Show Log in Files).
Thanks!
1) Does this problem happen every time you launch Espresso Test Recorder or only the first time or is it flaky?
2) Does this problem also happen when you try to debug your app (with the same run configuration you use for Test Recorder)?
3) Could you please attach idea.log file after you experience the reported issue (Help | Show Log in Files).
Thanks!
vi...@gmail.com
First time trying Espresso Recording and I'm in the same case:
Phone LG G3 Android 5
Emulator N5 Android 5
Android Studio 2.2
Build #AI-145.3276617, built on September 15, 2016
JRE: 1.8.0_76-release-b03 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
1) All the time with those devices
2) Yes -> so it's more a Debugger problem, if I then attach manually to the device using "Attach debugger to Android Process" it works
3) it's attached below
Phone LG G3 Android 5
Emulator N5 Android 5
Android Studio 2.2
Build #AI-145.3276617, built on September 15, 2016
JRE: 1.8.0_76-release-b03 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
1) All the time with those devices
2) Yes -> so it's more a Debugger problem, if I then attach manually to the device using "Attach debugger to Android Process" it works
3) it's attached below
sn...@google.com
Thank you for letting us know that you experience this issue too. Since I still cannot reproduce it, do you mind checking if it persists when you disable Instant Run? That is, disable Instant Run, restart Android Studio (so its state is clean), and then check if you still run into this issue. Thanks!
ri...@yummytech.com
I'm having a similar issue with Android 2.2.2 on macos sierra on MacbookAir 2013 13" and a Samsung S2 running Android API23. Debugger won't attach unless I manually "Attach debugger to Android Process"
ri...@yummytech.com
[Comment deleted]
sn...@google.com
Richard, thank you for reporting your observation. Could you please check if this correlates with Instant Run (please see my previous post)? Thanks!
zh...@gmail.com
I'm having same issue, but only if my tests are in dedicated module. And it happens both with Instant Run turned on and off.
sn...@google.com
Thank you for confirming, Kirill. Do you mind expanding on what you mean by a dedicated module and why the location of tests matters (i.e., does the problem happen only when you try to run tests while the app can start normally)?
Also, it would be great if you could restart Android Studio and see if the problem still persists (both for regular Debug and starting Test Recorder). Thanks!
Also, it would be great if you could restart Android Studio and see if the problem still persists (both for regular Debug and starting Test Recorder). Thanks!
zh...@gmail.com
Sure! By dedicated module I mean separate Gradle module/project which targets main app module and applies 'com.android.test' plugin. Here is an example of such project: https://github.com/kirillzh/AndroidTestModule .
I presume that it happens because tests are ran as JUnit tests and not Instrumentation tests.
Please refer these two tickets:
https://youtrack.jetbrains.com/issue/IDEA-163886
https://code.google.com/p/android/issues/detail?id=183931
Thank you!
I presume that it happens because tests are ran as JUnit tests and not Instrumentation tests.
Please refer these two tickets:
Thank you!
zh...@gmail.com
Oh, and no, I see none of these issues if I have tests in `androidTest` directory of main app module.
sn...@google.com
Thank you for your prompt clarification! As far as I understand, you observe this issue only when you run tests and only from the dedicated module. Could you please also confirm that you experience this issue if you try to run tests right after restarting Android Studio? Thanks!
zh...@gmail.com
Yes, that's right, only in module. Both issues are still reproducible even after restarting Android Studio.
I'm on 2.3 Canary right now, but I've seen this issue for almost a year now, was waiting for resolution ofhttps://code.google.com/p/android/issues/detail?id=183931 .
I'm on 2.3 Canary right now, but I've seen this issue for almost a year now, was waiting for resolution of
sn...@google.com
Thank you for checking, Kirill!
Siva, looks like this issue is much broader in scope than just Test Recorder and actually predates Test Recorder's existence.
Siva, looks like this issue is much broader in scope than just Test Recorder and actually predates Test Recorder's existence.
sh...@gmail.com
This problem happens to my development machine too.
gr...@pocketmatter.com
This issue has started up on my project also but, I am only trying to run the debugger on an emulator. I turned off Instant Run and the problem is the same. I am able to start debugging after using Attach Debugger to Android Process. I have a feeling it may have something to do with the configuration files for the app. Is there a way to do a clean reset to see if that clears up the problem?
ve...@gmail.com
[Comment deleted]
ve...@gmail.com
Solution that worked for me was clearing the Intellij IDEA (Android Studio) .idea directory which contains configuration information:
1. Exit Android Studio
2. Navigate to the project you are trying to run
3. Backup any files inside .idea that you modified (if your project checks any of these into VCS)
4. Delete .idea directory
5. Open the project in Android Studio
1. Exit Android Studio
2. Navigate to the project you are trying to run
3. Backup any files inside .idea that you modified (if your project checks any of these into VCS)
4. Delete .idea directory
5. Open the project in Android Studio
gr...@pocketmatter.com
@veeren #19, Your solution also worked for me. Thanks for responding to this bug report. It probably has something to do with VCS in that some of the xml files may have been modified externally. I know that I was having issues with the Google Cloud Repository immediately before the problem started. In my case, it appears unrelated to the Instant Run feature.
gr...@pocketmatter.com
FYI, Solution #19 also corrected emulator performance issues I was also having executing my code. The calculations and execution was extremely slow. I first noticed this issue when transitioning from the stable version of Android Studio to V2.3 Beta 1. I recall a warning message that said it required a conversion of the project files that would also make it impossible to go back to the previous version. The message recommended saving the project with a backup.
sh...@gmail.com
Thanks for the solution of #19. It resolves the debug problem.
ve...@gmail.com
da...@gmail.com
The solution of #19 works, thanks
[Deleted User] <[Deleted User]>
#19 worked for me too. i think upgrading android studio to 2.3.1 messed something up
Description
1.8.0_76-release-b03x64 Oracle Corporation, Mac OS X(x86_64) v10.11.6 unknown (2560x1440, 2560x1440, 1440x900 R)
Espresso Test Recorder hangs with "waiting for debugger" on device.
Repro:
choose "Run"-> "Record Espresso Test"
Expected:
Espresso recorder UI will appear in AS.
Actual:
App is built, pushed to device, but then device says "Waiting for debugger"
AS console says:
$ adb shell am start -n " com.example.sample.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D
Connected to process 16083 on device huawei-nexus_6p-8XV5T15A12341234
I/art: Late-enabling -Xcheck:jni
W/ActivityThread: Application com.example.sample is waiting for the debugger on port 8100...
I/System.out: Sending WAIT chunk