Appium appium 移动自动化测试提示 error: Could not find a connected Android device 求解决方案，在线等在线等~
本人新手入坑 appium，好不容易装好黄静，昨天测试成功就睡觉了。今天一开机，就连不上了。但是 cmd devices 是可以看到设备的，有大神知道什么原因吗？谢谢！
以下是 appium 运行代码。求大神。呜呜~
[Appium] Welcome to Appium v1.8.0
[Appium] Non-default server args:
[Appium] address: 127.0.0.1
[Appium] Appium REST http interface listener started on 127.0.0.1:4723
[HTTP] --> POST /wd/hub/session
[HTTP] {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"platformName":"Android"}},"desiredCapabilities":{"platformName":"Android","platformVersion":"5.1.1","deviceName":"127.0.0.1:5555","appPackage":"com.baidu.tieba","appActivity":"com.baidu.tieba.LogoActivity"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"platformName":"Android","platformVersion":"5.1.1","deviceName":"127.0.0.1:5555","appPackage":"com.baidu.tieba","appActivity":"com.baidu.tieba.LogoActivity"},null,{"firstMatch":[{}],"alwaysMatch":{"platformName":"Android"}}]
[BaseDriver] Event 'newSessionRequested' logged at 1526153469305 (03:31:09 GMT+0800 (中国标准时间))
[Appium] Could not parse W3C capabilities: 'deviceName' can't be blank. Falling back to JSONWP protocol.
[Appium] The following capabilities were provided in the JSONWP desired capabilities that are missing in W3C capabilities: ["platformName","platformVersion","deviceName","appPackage","appActivity"]. Falling back to JSONWP protocol.
[Appium] Creating new AndroidDriver (v2.6.0) session
[Appium] Capabilities:
[Appium] platformName: Android
[Appium] platformVersion: 5.1.1
[Appium] deviceName: 127.0.0.1:5555
[Appium] appPackage: com.baidu.tieba
[Appium] appActivity: com.baidu.tieba.LogoActivity
[BaseDriver] Creating session with MJSONWP desired capabilities: {"platformName":"Android","...
[BaseDriver] Session created with session id: 650fa53c-151b-433b-9d44-3199cdd61a4c
[AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 10.0.1
[ADB] Checking whether adb is present
[ADB] Using adb.exe from F:\ruanjian\android\android-sdk-windows\platform-tools\adb.exe
[AndroidDriver] Retrieving device list
[ADB] Trying to find a connected android device
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[ADB] Getting connected devices...
[ADB] Could not find devices, restarting adb server...
[ADB] Restarting adb
[ADB] Killing adb server on port 5037
[AndroidDriver] Shutting down Android driver
[AndroidDriver] Called deleteSession but bootstrap wasn't active
[BaseDriver] Event 'newSessionStarted' logged at 1526153492737 (03:31:32 GMT+0800 (中国标准时间))
[W3C] Encountered internal error running command: Error: Could not find a connected Android device.
[W3C] at ADB.getDevices$ (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\lib\tools\system-calls.js:188:13)
[W3C] at tryCatch (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:67:40)
[W3C] at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:315:22)
[W3C] at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:100:21)
[W3C] at invoke (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[W3C] at enqueueResult (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:185:17)
[W3C] at new Promise ()
[W3C] at new F (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\core-js\library\modules\$.export.js:30:36)
[W3C] at AsyncIterator.enqueue (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:184:12)
[W3C] at AsyncIterator.prototype.(anonymous function) [as next] (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:100:21)
[W3C] at Object.runtime.async (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:209:12)
[W3C] at getDevices (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\build\lib\tools\system-calls.js:402:38)
[W3C] at ADB.getDevices$ (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\lib\tools\system-calls.js:205:20)
[W3C] at tryCatch (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:67:40)
[W3C] at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:315:22)
[W3C] at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:100:21)
[W3C] at GeneratorFunctionPrototype.invoke (C:\Users\ymxz375417299\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[W3C] at
[HTTP] <-- POST /wd/hub/session 500 23435 ms - 1570
[HTTP]
我写的测试代码是
你这是用 tcpip 连接的设备吧？
你服务器地址和设备地址都是 127.0.0.1
你 appium 服务的端口号和代码的端口号不一致吧
你用的是什么模拟器啊，建议你重启下 Appium 服务和模拟器看看。
adb devices 看看
最好用 genymotion
对
robad
回复
robad
回复
检查每个参数对应是不是正确，是命令行启动还是桌面版？每次启动 你的 appium 有没有设置 $appium --session-override --no-reset
试一下不要用 devicename 这个参数，用 udid 这个参数，devicename 随便输入
deviceName 怎么是 127.0.0.1:5555 这么奇葩
Could not parse W3C capabilities: 'deviceName' can't be blank. Falling back to JSONWP protocol.这个提示
建议你弄个真机试一下
对
robad
回复
robad
回复
你这样吧，用 appium 的桌面版 ，它是有个录制跟调试功能的，先把你的必要参数放进去，如：安卓版本号、设备号、包名跟主 activity，用来调试看看。
对
战 神
回复
战 神
回复
谢谢你的热心回答！问题已经解决了。按照你说的调试后发现好像是我的 APPIUM 有问题，就用命令行 npm install -g appium 重装，然后重启电脑就好了。！谢谢你们的回答。让我感到温暖~
我的一直弹出这个，然后出现这个提示：
Encountered internal error running command: Error: Could not find a connected Android device.
楼主，你如果有解决方法了，一定给我回复！
我也是这样，楼主怎么解决的？一直找不到 android 设备
同样的问题，求指教交流，邮箱地址 rainbowxiamm@163.com
我和楼主遇到了同样的问题，但是现象一样解决方法不同，解决方法如下：
我的 appium 桌面版本是 v1.9.1
点击图标后第一个界面中有个 “Edit Configurations” 项，点击该项进去后需要配置 “ANDRIOID_HONE” 和 “JAVA_HOME”(我家里电脑上是 v1.7 的版本就不需要配置这两项)。
ps：我已经在环境变量中添加了这两项但还是需要在这里填写一下。
好不到设备是 sdk 的 adb 与模拟器的 adb 版本低，新版的 appium 不兼容，需要升级 adb 工具包
模拟器中手动安装一个 appium 的预装 apk settings_apk-debug.apk 然后重新连接就可以了；
这个 apk 在 appium 的安装目录下：%AppData%Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks