CODEWITHSUNDEEP
androidandroid-studiologcat
Farshad
Farshad

Reputation: 3140

No debuggable processes is visible since Android Studio 4.2

After updating my android studio to version 4.2 I have no debuggable processes in Logcat to select. The build variant is debug for sure, and I already checked the other StackOverflow posts that address my issue but didn't find anything. Also, I tried older versions and it turned out that 4.1.3 doesn't have this issue and processes are visible, but I have this problem with the 4.2 and 4.2.1 and BumbleBee, It seems there is something wrong with new versions. I'm wondering if someone else had the same problem, Any help would be appreciated.

Note: Even debugger can't attach to the process

enter image description here

Upvotes: 8

Views: 3800

Answers (5)

Homayoon Ahmadi
Homayoon Ahmadi

Reputation: 2833

This is a bug with some Windows OS datetime formats (such as Persian or Arabic formats) in Android Studio version 4.2 and higher.

We just need to use English (United States) format to avoid this problem. (Tested on version 4.2 and Arctic Fox both)

How to do: In windows 10 Go to Control Panel > Region > Formats and choose English (United States) from dropdown menu.

Edit: I have reported this bug in issue tracker. So you can give it a star to make sure Google will fix it in next release of Android Studio: https://issuetracker.google.com/issues/210299312

Upvotes: 8

Volodya Polohalo
Volodya Polohalo

Reputation: 11

Had the same issue few days ago. Didn't see this method tried here so I'll try to describe it. Nothing helped me, I tried to invalidate cache, reinstall command line tools, Android Studio, update it to latest version.

What resolved the issue for me was going to File -> Manage IDE Settings -> Restore Default Settings and going through IDE setup again.

Upvotes: 1

Vahid
Vahid

Reputation: 1758

I faced this issue by starting version 4.2 and I tried all stable and beta versions that came out after that and sadly problem still is there now. One thing that takes my attention is that everywhere I look up for a way to solve this I saw Iranian developers. because of that I guessed this problem (specially mean after version 4.2) is a sort of google sanctions

Update
as I guessed it's related to sanctions and you should change Region and Regional Format to another country to solve problem

Upvotes: 4

Farshad
Farshad

Reputation: 3140

Well, As I mentioned in the comments I tried almost everything but It didn't work, Eventually, I had to install Windows again (Windows 10), I don't know why but I guess there was something wrong with the OS.

Note: I had this issue with Android Studio 4.2 and 4.2.1 but 4.1.3 was OK.

Upvotes: 0

Mahdi
Mahdi

Reputation: 6389

I had same issue on specific version but can not remember right now. My solution was kill and restart adb.

In command go to folder: sdk/platform-tools/ Then run:

adb kill-server

And then run:

adb start-server

This should reconnect adb and you will find proper process to connect to in Android studio.

Upvotes: 1

Related Questions