HarmonyOS 鸿蒙Next Deveco真机无法启动调试，有没有技术人员给看一下

HarmonyOS 鸿蒙Next Deveco真机无法启动调试，有没有技术人员给看一下

2023-10-19 11:21:30,121 [ 94281] SEVERE - #com.huawei.deveco.panda.message.DevToolsServiceWrapper - create websocket proxy object failed, url: ws://localhost:15038 timeout: 10 detail: 

com.github.kklisura.cdt.services.exceptions.WebSocketServiceException: Failed connecting to ws server {}

    at com.github.kklisura.cdt.services.impl.WebSocketServiceImpl.connect(WebSocketServiceImpl.java:120)
    at com.github.kklisura.cdt.services.impl.WebSocketServiceImpl.create(WebSocketServiceImpl.java:86)
    at com.huawei.deveco.panda.message.DevToolsServiceWrapper.lambda$create$0(DevToolsServiceWrapper.java:125)
    at com.huawei.deveco.panda.message.DevToolsServiceWrapper.create(DevToolsServiceWrapper.java:126)
    at com.huawei.deveco.panda.message.DevToolsServiceWrapper.<init>(DevToolsServiceWrapper.java:64)
    at com.huawei.deveco.panda.message.DevToolsServiceWrapper.<init>(DevToolsServiceWrapper.java:52)
    at com.huawei.deveco.ace.debug.hos.run.launcher.HarmonyPandaLauncher$MyStartTask.run(HarmonyPandaLauncher.kt:165)
    at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:429)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:114)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsynchronously$6(CoreProgressManager.java:480)
    at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:252)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:186)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679)
    at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173)
    at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:252)
    at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
    at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
    at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
    at java.base/java.lang.Thread.run(Thread.java:833)

Caused by: javax.websocket.DeploymentException: Connection failed.

    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientSocket._connect(GrizzlyClientSocket.java:413)
    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientSocket.access$000(GrizzlyClientSocket.java:81)
    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientSocket$1.call(GrizzlyClientSocket.java:212)
    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientSocket$1.call(GrizzlyClientSocket.java:208)
    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientSocket.connect(GrizzlyClientSocket.java:226)
    at org.glassfish.tyrus.container.grizzly.client.GrizzlyClientContainer.openClientSocket(GrizzlyClientContainer.java:72)
    at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:647)
    at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:696)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:849)
    at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:123)
    at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:493)
    at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355)
    at com.github.kklisura.cdt.services.impl.WebSocketServiceImpl.connect(WebSocketServiceImpl.java:98)
    ... 26 more

Caused by: java.net.ConnectException: Connection refused: no further information

    at java.base/sun.nio.ch.Net.pollConnect(Native Method)
    at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
    at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnectorHandler.onConnectedAsync(TCPNIOConnectorHandler.java:210)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnectorHandler$1.connected(TCPNIOConnectorHandler.java:158)
    at org.glassfish.grizzly.nio.transport.TCPNIOConnection.onConnect(TCPNIOConnection.java:258)
    at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:527)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.executeIoEvent(WorkerThreadIOStrategy.java:103)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.executeIoEvent(AbstractIOStrategy.java:89)
    at org.glassfish.grizzly.nio.SelectorRunner.iterateKeyEvents(SelectorRunner.java:414)
    at org.glassfish.grizzly.nio.SelectorRunner.iterateKeys(SelectorRunner.java:383)
    at org.glassfish.grizzly.nio.SelectorRunner.doSelect(SelectorRunner.java:347)
    at org.glassfish.grizzly.nio.SelectorRunner.run(SelectorRunner.java:278)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:591)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:571)
    ... 1 more

2023-10-19 11:21:30,123 [ 94283] SEVERE - #com.huawei.deveco.panda.message.DevToolsServiceWrapper - DevEco Studio 3.1.0.501 Build #DS-223.8617.56.36.310501

2023-10-19 11:21:30,123 [ 94283] SEVERE - #com.huawei.deveco.panda.message.DevToolsServiceWrapper - JDK: 17.0.6; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o.

2023-10-19 11:21:30,123 [ 94283] SEVERE - #com.huawei.deveco.panda.message.DevToolsServiceWrapper - OS: Windows 11

2023-10-19 11:21:38,761 [ 102921] INFO - #c.i.c.ComponentStoreImpl - Saving appFileTypeManager took 12 ms, HttpConfigurable took 29 ms

2023-10-19 11:21:38,926 [ 103086] INFO - #com.huawei.hvigor.service.HvigorWrapperService - Find hvigor boot script:C:\Users\admin\.hvigor\project_caches\e8a22300acdd71aa444f2c4be6553b90\workspace\node_modules\@ohos\hvigor\bin\hvigor.js

2023-10-19 11:21:38,946 [ 103106] WARN - #com.huawei.deveco.projectmodel.ohos.model.TargetManager - getCurrentTarget is null, cause: moduleModel is null.

更多关于HarmonyOS 鸿蒙Next Deveco真机无法启动调试，有没有技术人员给看一下的实战教程也可以访问 https://www.itying.com/category-93-b0.html

8 回复

也碰到同样问题了，到现在大半年了也没解决。

更多关于HarmonyOS 鸿蒙Next Deveco真机无法启动调试，有没有技术人员给看一下的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


目前部分机型卡顿黑屏为内部已知问题，内部技术人员正在修复中！

webview组件，本人只运行了几个涉及到的codelab中的Demo，没有一个可以正常加载和使用的，webview根本无法正常工作，请版主关注。

QQ截图20231019141815.png

所有涉及到WebView的工程，比如上面的WebCookie工程，运行后，点击页面上的任意输入框，在输入法出现后，界面会整个变成黑色，无法输入。论坛不知能不能传录屏，不太会。

点击上面的输入框，就成了下面的状态了：

这个时候就死掉了，app只能从后台退出，我这边100%复现，没一次正常过。

QQ截图20231019134823.png

QQ截图20231019135009.png

QQ截图20231019135403.png

IDE界面上没有发现报错提示，这个状态时，app在真机上启动一下就退出了。 当下运行的是Codelab中的WebCookie，代码一点没动。其它的demo和新建的工程也是这样。

找HarmonyOS工作还需要会Flutter的哦，有需要Flutter教程的可以学学大地老师的教程，很不错，B站免费学的哦：BV1S4411E7LY/?p=17

DevEco Studio版本和SDK版本提供一下，具体在DevEco Studio上的报错截图也提供一下！

在HarmonyOS鸿蒙Next中，使用Deveco进行真机调试时无法启动调试，可能是由于以下几个原因：

  1. 设备未正确连接：确保设备通过USB线缆正确连接，并且设备的开发者选项和USB调试功能已开启。

  2. 驱动程序问题：检查设备驱动程序是否已正确安装，尤其是在Windows系统上，可能需要手动安装或更新驱动程序。

  3. Deveco Studio版本问题：确保使用的Deveco Studio版本与鸿蒙Next SDK兼容，建议使用最新版本。

  4. 调试配置错误：检查项目的调试配置，确保选择了正确的设备和调试模式。

  5. 设备授权问题：首次连接设备时，设备会提示授权调试请求，确保在设备上授权了调试请求。

  6. 网络问题：如果使用无线调试，确保设备和开发机在同一网络下，并且网络连接稳定。

  7. 日志查看：通过Deveco Studio的日志窗口查看详细的错误信息，根据错误信息进行排查。

  8. 设备系统版本：确保设备的鸿蒙系统版本与Deveco Studio中配置的SDK版本匹配。

  9. 端口冲突：检查是否有其他应用程序占用了调试所需的端口。

  10. 重启设备和Deveco Studio：有时简单的重启操作可以解决临时的连接或调试问题。

如果以上方法无法解决问题，可以尝试在华为开发者社区查找类似问题或参考官方文档。

回到顶部