Android Studio 1.2 beta version hangs on debugging

Question

I’ve just upgraded Android Studio from version 1.0 to 1.2 beta and I can no longer perform any kind of debug operation. If I set a break point, Android Studio hangs and it can’t resolve the command:

Waiting until last debugger command completes

but it never completes.

So, is it possible to downgrade to the previous stable version (1.0) without downloading again?

Thanks!

Answer 1

First Solution

1-Click file menu

2-Click Invalidate Caches / Restart

3-Click Invalidate And Restart

note : work in the same session only.

Second Solution

-Use GenyMotion Emulator With Android Version 5 or up.

Third Solution

-Use Android Studio 1.1 in my job my teammate use this version and it's okay .

the new debugger add variable value beside it in debugging steps it may cause the problem .

imagine that you watch all variables in debugging it should make problem. it's called Inline Debugger

download link to Android Studio 1.1 : http://tools.android.com/download/studio/canary/1-1-0

Third Solution is my own choice at work.

Update: I tried Android Studio 1.3 Preview but still have the same problem.

Update: here in android studio info problem fixed link 1 link 2

Answer 2

It looks like a bug in Android studio. It's reported here: https://code.google.com/p/android/issues/detail?id=73828

Answer 3

Here is an answer from Google regarding problems with current versions of Android Studio running with pre M version phones -

For anyone else who might encounter this issue, here is a summary:

The issue shows up in one of two ways: Studio will be responsive, but the debugger will be stuck at either "Collecting Data.." or "Waiting for last debugger command to complete..". This happens on both Dalivk and ART, so all versions of the platform are affected. The issue is more prevalent with Studio 1.2, but exists on all versions of Studio.

The correct fix for this issue is in the platform. The next version of M preview is likely to have this fix (in progress CL here: https://android-review.googlesource.com/#/c/152715/)

Until then we have some workarounds which reduce the probability of hitting this issue. So if you encounter this issue, you can try one of the following:

1. Change your breakpoint to only suspend the thread where it is hit rather than all threads. See comment #82 for more info on how to do this. The next release of Studio 1.2 and Studio 1.3 will be make this the default. (https://android-review.googlesource.com/#/c/152715/)

2. You can turn off various settings in the debugger that invoke methods: These include: a) inline debugging (https://www.jetbrains.com/idea/help/inline-debugging.html) b) "Enable 'toString()' object view" (Settings | Debugger | Data Views | Java) c) "Enable alternative view for Collections classes" (Settings | Debugger | Data Views | Java)

The 2nd option is more severe (it limits the amount of automation the debugger does for you), so we are not enabling that by default. However, if you still see the issue after changing the suspend policy to thread only, then unfortunately, you'll have to do the steps in 2 as well.

Finally, if you still see the issue after both, then that would be a new bug. Please file a new bug with a test case.

Thanks everyone for your patience and your help in providing us with repro cases and stack traces.

https://code.google.com/p/android/issues/detail?id=172523

Answer 4

This happened to me too.

I am running on a Mac so all I had to do was remove the Android Studio.app from /Applications and reinstall Android Studio although I reinstalled version 1.1.0

I understand that the settings folder name changed from version 1.1.0 to 1.2 so that made the above possible.