You shouldn't be seeing this warning: *Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse* *Restart ADB integration and try again* *Waiting for process: com.micromobs.app.debug*
However, it is odd that you can still debug if using GenyMotion. Do you not see the same warning then? What I'd do: 1. Make sure "Tools | Android | Enable adb integration" is checked/enabled. 2. Close Studio. 3. Close any other tool (DDMS/monitor/..) that you might have running. 4. killall adb. Restart and do the debug again. See if that warning still persists. On Wed, Jun 18, 2014 at 5:23 PM, Kaushik Gopal <[email protected]> wrote: > * it pops up the launcher for picking which device > * after picking the device, it appears that the apk is successfully > installed onto the device. > * It then pops up the alert saying "waiting for debugger" - Application is > waiting for the debugger to attach. > > Here are the logs from the debug console: > ------- > *Waiting for device.* > *Target device: samsung-nexus_s-12345ABCD* > *Uploading file* > * local path: <PATH TO MY PROJ_DIR/build/outputs/apk/app-debug.apk* > * remote path: /data/local/tmp/com.mycompany.app.debug* > *Installing **com.mycompany.app.debug* > *DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/* > *com.mycompany.app.debug**"* > *pkg: /data/local/tmp/**com.mycompany.app.debug* > *Success* > > > *Launching application:**com.mycompany.app.debug**/**com.mycompany.app* > *.ui.activities.MainEntryPageActivity.* > *DEVICE SHELL COMMAND: am start -D -n "**com.mycompany.app.debug**/* > *com.mycompany.app**.ui.activities.MainEntryPageActivity**" -a > android.intent.action.MAIN -c android.intent.category.LAUNCHER* > *Starting: Intent { act=android.intent.action.MAIN > cat=[android.intent.category.LAUNCHER] cmp=**com.mycompany.app.debug**/* > *com.mycompany.app**.ui.activities.MainEntryPageActivity** }* > > *Warning: debug info can be unavailable. Please close other application > using ADB: Monitor, DDMS, Eclipse* > *Restart ADB integration and try again* > *Waiting for process: com.micromobs.app.debug* > ---------- > > idea.log looks perfectly normal: > > Marker - Jun 18, 2014, 5:19:32 PM > 2014-06-18 17:20:03,383 [ 555159] INFO - a.gradle.invoker.GradleInvoker > - About to execute Gradle tasks: [:app:assembleDebug] > 2014-06-18 17:20:03,388 [ 555164] INFO - s.plugins.gradle.GradleManager > - Instructing gradle to use java from > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > 2014-06-18 17:20:03,389 [ 555165] INFO - dle.util.AndroidGradleSettings > - Found Android SDK home at '/Applications/Android Studio.app/sdk' (from > local.properties file) > 2014-06-18 17:20:03,389 [ 555165] INFO - a.gradle.invoker.GradleInvoker > - Build JVM args: [] > 2014-06-18 17:20:03,389 [ 555165] INFO - a.gradle.invoker.GradleInvoker > - Build command line options: [--configure-on-demand, > -Pandroid.invoked.from.ide=true] > 2014-06-18 17:20:03,389 [ 555165] INFO - .project.GradleExecutionHelper > - Passing command-line args to Gradle Tooling API: [--configure-on-demand, > -Pandroid.invoked.from.ide=true] > 2014-06-18 17:20:26,079 [ 577855] INFO - indexing.UnindexedFilesUpdater > - Indexable files iterated in 16 ms > 2014-06-18 17:20:26,079 [ 577855] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update started: 0 files to update > 2014-06-18 17:20:26,079 [ 577855] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update done in 0 ms > 2014-06-18 17:20:26,134 [ 577910] INFO - indexing.UnindexedFilesUpdater > - Indexable files iterated in 15 ms > 2014-06-18 17:20:26,134 [ 577910] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update started: 0 files to update > 2014-06-18 17:20:26,135 [ 577911] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update done in 1 ms > 2014-06-18 17:20:26,165 [ 577941] INFO - indexing.UnindexedFilesUpdater > - Indexable files iterated in 9 ms > 2014-06-18 17:20:26,165 [ 577941] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update started: 1 files to update > 2014-06-18 17:20:26,171 [ 577947] INFO - indexing.UnindexedFilesUpdater > - Unindexed files update done in 6 ms > > ---------------- > > Killing adb, restarting device, restarting app, restarting computer, none > of that helps. I still can successfully debug, if i deploy to my emulator > (Genymotion). > > Thanks. > > > > On Wed, Jun 18, 2014 at 3:07 PM, 'Siva Velusamy' via adt-dev < > [email protected]> wrote: > >> When the app is waiting for the IDE to attach, what is the IDE doing? Did >> it go through the build fine, then install the apk, etc? >> >> Also, Anything out of ordinary in idea.log? (Help | Show Log in Files) >> >> >> >> >> On Tue, Jun 17, 2014 at 9:07 PM, Kaushik Gopal <[email protected]> wrote: >> >>> A small correction, I actually do see the log of commands within my app, >>> on the device log cat (which is what makes it even more weird). It's just >>> not clamping on to the app when running. >>> >>> >>> On Tuesday, June 17, 2014 9:05:36 PM UTC-7, Kaushik Gopal wrote: >>>> >>>> Everything was working well. But recently (I'm guessing it's with the >>>> latest patch, but i'm not entirely sure of this) i noticed that i can't >>>> debug with my devices attached. I develop with the Genymotion emulator, and >>>> oddly i can debug/step-through there. But when i connect my actual device >>>> and try to attach the debugger, i get the dreaded "Waiting for debugger" >>>> alert. saying my application is waiting for the debugger to attach. >>>> >>>> >>>> here are possibly useful bits of information: >>>> >>>> - on Android Studio 0.6.1 patch >>>> - OSX Mavericks. >>>> >>>> - Genymotion emulator works and allows debugging (no problems here). >>>> - Actual devices don't and prompt aforementioned debugger alert. >>>> - I have used these devices multiple times before, with previous >>>> versions, so i'm sure it's not an issue with the usb debug option on the >>>> phone etc. >>>> - I can see the logs from the actual phone, on my Devices|logcat (like >>>> the radio signal/WifiState machine etc). >>>> - But nothing for my application. This leads me to believe "adb" >>>> doesn't have a problem. >>>> - Issuing the adb devices command successfully lists my device. >>>> >>>> I've never had problems before and i've been using the latest builds >>>> from the last 15 releases of Android Studio. Usually when i've had problems >>>> like this, a simple restart of the device/Android studio solves it. This >>>> time nothing gives :( >>>> >>>> Any help would be much appreciated! >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "adt-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "adt-dev" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/adt-dev/M3Ui55RJ5Gc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
