Appium 1.7.1 Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: socket hang up
See original GitHub issueThe problem
I am running test scripts using appium 1.7.1 with uiautomator2 for testing android apps. While running i am getting Error
Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: socket hang up at doJwpProxy$ (../../../lib/mjsonwp/mjsonwp.js:384:13) at tryCatch (/usr/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/usr/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21) at GeneratorFunctionPrototype.invoke (/usr/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
I am using appium-python-robotframework for writing test scripts.
The above error occurs when I am using uiautomator2 for testing Android phones with v7 and above. The automation runs fine when I am using automationName=appium
for testing Android phones below v7.
Some times I am getting the ECONNRESET error in between the test cases:
WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to remote server. Original error: Error: read ECONNRESET
I am getting these two errors switching in between as random. Some of the test cases passes without fail. But some fails with these errors.
Environment
- Appium version (or git revision) that exhibits the issue: Appium v1.7.1
- Desktop OS/version used to run Appium: Ubuntu 16.04
- Node.js version (unless using Appium.app|exe):
$ node --version
v7.10.1
- Mobile platform/version under test: Android v 7.0
- Real device or emulator/simulator: real device
- Appium CLI or Appium.app|exe: Appium CLI
Details
The uiautomator2 version I am using is:
$ npm list -g appium-uiautomator2-driver
/usr/lib
-- appium@1.7.1
-- appium-uiautomator2-driver@0.6.5
Link to Appium logs
https://gist.github.com/KrishnaprabhaSNaik/7507aab60ab4bb30acf42711a93040b8
This is my link to the appium log.
Code To Reproduce Issue [ Good To Have ]
OpenApplication ${Appium_server} platformName=${Platform_name} platformVersion=${Platform_version} deviceName=${Device_names["${Platform_Version}"]} app=${file_path}/Resources/${Application_APK_name} appActivity=${Activity_name} appPackage=${Package_name} automationName=uiautomator2
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:49
Top GitHub Comments
Changing from uiautomator2 to appium is not a solution. Appium server is not supported for android 7+.
Changing “automationName”: “uiautomator2” to
“automationName”: “appium”
fixed this for non-primary User accounts. 😃