-
Notifications
You must be signed in to change notification settings - Fork 480
Cannot connect device with Android Studio 3.3.2 and Android 8.1 #71
Comments
same to me its not working to latest android studio |
same here with the latest android studio |
Can confirm this issue with the latest update of AS. |
Can you provide information related to the device model you are using the OS version and the AS version? |
AS version: 3.3.2 |
@bogdanzurac what's your computer OS version? |
Computer OS: MacOS Mojave |
Computer OS: Win7 x64 and Win10 x64 |
I'm also facing same problem. Even when both computer and mobile device are on same network. I'm getting the following message, "unable to connect to the device make sure both computer and mobile device are on same network." |
This was the ONLY working solution till android studio updated the IDE. It doesn't work, sometimes when the disconnect button is clicked it "connects" but it doesn't really work. |
Same problem here This one worked for me - WIFI ADB ULTIMATE by https://github.com/huazhouwang/WIFIADB/tree/master/WIFIADBIntelliJPlugin |
Same problem here |
Same here:
|
Could you check if you can connect your device using the terminal? Right now I don't understand if the issue is related to Android Studio or the plugin. You have to plug in your device and run these commands from your terminal:
|
@pedrovgs Here is what I got:
|
Same here:
Do you need some additional logs we can provide for you? It does seem strange that this started happening to a couple of us right after AS updated. |
I've got the same problem. I tried the suggestions. but I got no answer.
|
I got same issue here. I'm using Android Studio 3.4 and my phone is samsung s7 edge, it shows same error message(ask me to check same network connection). |
After clicking Connect, android studio prompted "Unable to connect to device......Same network"
and on device, it prompted for permission.
After allowed on device, click "Connect" on android studio, looping the issue.
Please help. Thanks.
The text was updated successfully, but these errors were encountered: