blocks|key|4661199|text|在Android+Studio桌面上，单击"Select+Run/Debug+Configuration“按钮(带有android图标)，您应该能够选择正确的选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4661200|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

On Android Studio desktop, click on "Select Run/Debug Configuration" button (one with an android icon), you should be able to select the correct option.

blocks|key|4661281|text|我已经有这个“套接字关闭”错误好几个星期了，它让我有点抓狂。今天我发现，虽然通过调试图标启动仍然会给我一个“Socket+closed”，如果我后来附加了调试器，它仍然可以工作(在屏幕截图中)。希望这能节省别人的时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4661282|​|4661283|📷|atomic|offset|length|4661284|4661285|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1f7aea235d071220a0298f9948fb6fd6.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I've had this “Socket closed” error for several weeks and it was driving me slightly mad. Today I discovered that although launching via the debug icon still gives me a “Socket closed” if I attach the debugger afterwards it works (in screenshot). Hope it saves someone else time. 

<img src="https://i.stack.imgur.com/KmcBY.png" alt="Screenshot highlighting the attach debugger icon">

blocks|key|4661301|text|我可以通过选择"app“配置来解决这个问题。在上面的屏幕截图中，run按钮左侧的下拉按钮允许您选择不带括号的configuration.Select+one。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4661302|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was able to fix this issue by selecting the "app" configuration. In the above screen shot the pull down to the left of the run button allows you to select the configuration.Select one without the brackets.

blocks|key|4661345|text|为了避免这个问题，并且实际上是从Android+Studio中启动的，我必须显式地切换我正在操作的构建变体(通过在左侧选择“构建变体”时弹出的面板)。然后，当实际按下我的Android应用程序配置顶部的调试按钮(通过运行/调试图标左侧的下拉菜单选择)时，它将正确地部署我所在的构建变体模式。(如果我可以从下拉菜单中设置不同的Android应用程序配置来部署不同的构建类型，而不是必须更多地手动切换变体，那就太好了，但我现在还不知道怎么做。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4661346|​|4661347|📷|atomic|offset|length|4661348|4661349|另外，在build.gradle文件的buildTypes部分，您可能需要debuggable+true，否则，如果您尝试手动附加调试器，您的进程将不会显示在对话框中。|style|CODE|4661350|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3209ce8e6e063f5f65ad1912a54dede1.png|imageAlt^0|0|0|0|1|0|0|0|11|F|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@$G|Z|H|10|1|11]]|A|$]]|$1|I|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@$G|14|H|15|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

To avoid this problem and actually launching from within Android Studio, I had to explicitly switch the build variant I was operating in (via the panel that pops up when selecting 'build variants' on the left edge). Then when actually pressing the debug button up top for my Android Application configuration (selected via drop down menu to the left of the Run/Debug icons), it would properly deploy the build variant mode I was in. (Would be nice if I could set up different Android App configurations to deploy different build types from the drop down menu instead of having to switch variants more manually, but I don't see how right now.)

<img src="https://i.stack.imgur.com/MQVFK.png" alt="enter image description here">

Also in your buildTypes section in your build.gradle file, you probably want <code>debuggable true</code>, else your process won't show up in the dialog if you try to manually attach the debugger.

blocks|key|155120|text|我遇到了同样的情况，上面的解决方案对我不起作用，但我有一个小问题:我的应用程序扩展了android.app.Application。我发现对我有用的是编辑运行/调试配置(“编辑配置...”)，并选择“不启动活动”而不是“启动默认活动”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155121|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I ran into the same behavior, the above solutions didn't work for me, but I have a bit of a corner case: my app extends android.app.Application. What I found works for me is to edit the run/debug configuration ("Edit Configurations..."), and select "Do not launch Activity" instead of "Launch default Activity".

blocks|key|155140|text|我在linux上得到了这个错误，问题是之前的另一个进程占用了端口并挂起了。因此，解决方案是使用netstat来定位阻塞端口的进程，然后终止该进程，或者您可以重新启动计算机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155141|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was getting this error on linux, and the problem was that the another previous process have taken the port and hung. So, the solution is a netstat to locate the process blocking the port, then kill this process, or you can restart the machine.

blocks|key|155168|text|确保你的Android手机连接良好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155169|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Make sure your Android Phone is well connected.

blocks|key|4661450|text|我刚才遇到了这个问题，一个简单的解决方案:如果您有多个实例在运行，请确保您的运行配置指定了不同的JMX端口。refer+to+Image|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4661451|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/K4i39.png^0|1I|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I run into this problem just now, simple solution: if you have multiple instances running, make sure your run config specifiy different JMX port.
<a href="https://i.stack.imgur.com/K4i39.png" rel="nofollow noreferrer">refer to Image</a>

blocks|key|155262|text|我收到这个错误是因为我在"Run/Debug+Configurations“对话框中的"Test+Kind”选项被设置为"All+in+Package“而不是"Test+Class”。当我将其设置为"Test+Class“时，调试器可以完美地工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155263|​|155264|📷|atomic|offset|length|155265|155266|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e196206e06331f5aa6d4e8f15466c348.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I was getting this error because I had the "Test Kind" option in the "Run/Debug Configurations" dialog box set to "All in Package" rather than "Test Class". When I set it to "Test Class", the debugger worked flawlessly.

<a href="https://i.stack.imgur.com/ppxio.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ppxio.png" alt="enter image description here"></a>

blocks|key|155292|text|我在使用Java程序时遇到了类似的问题。我重新启动了IDE并更改了JMX端口号。然后程序在调试模式下运行，没有任何问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155293|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a similar problem with a Java program. I restarted the IDE and changed the JMX port number. Then the program ran in debug mode without any problems.

I get this error when trying to debug an Android app on Android Studio (v.0.4.4):

<pre><code>Error running &lt;appname&gt; [assembleDebug]: 
Unable to open debugger port : java.net.SocketException "Socket closed"
</code></pre>

The app compiles, and can be pushed to the phone using adb. There's no problem with adb; I can install/monitor logcat etc perfectly. I can load another project and can debug it just fine. I switch back to this one and it's still broken. So that would appear to rule out a problem with the pc (actually a Linux vm running under windows), the Android Studio install etc. I've rebooted this vm and the host pc.

I had this problem last last year and I "fixed it" then by uninstalling Eclipse (I suspected perhaps it was trying to get the same socket). 

I've spent some time Googling and attempting suggestions but they don't make any difference.

The problem occurred around the time that I produced a signed, proguarded release build. Until then I'd only been running the debug build. However, I believe all I did to create this release build was to edit build.gradle and configure Android Studio to automatically sign apks. I've since reverted the changes to build.gradle but the problem remains.

I see no relevant errors in any Android Studio log files; it's as if this exception is being captured, reported on screen but not logged anywhere.

Hopefully somebody reading this can suggest a few things here to change that I've overlooked.

Unable to open debugger port : java.net.SocketException "Socket closed"

Android Studio

日志文件

调试器

Android

Eclipse

Linux

Java

尝试在Android Studio (v.0.4.4)上调试Android应用程序时出现以下错误：Error running <appname> [assembleDebug]: Unable to open debugger port : java.net.SocketException "Socket closed...

问无法打开调试器端口: java.net.SocketException "Socket closed“
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法打开调试器端口: java.net.SocketException "Socket closed“EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法打开调试器端口: java.net.SocketException "Socket closed“
EN