Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MJSONWP] Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: connect ECONNREFUSED 127.0.0.1:8200 #8598

Closed
Zenerax opened this issue Jun 2, 2017 · 4 comments
Labels
Android related to Android-native driver(s)

Comments

@Zenerax
Copy link

Zenerax commented Jun 2, 2017

The problem

While running multiple test scripts to multiple devices in parallel, I see the following Appium error occurs from the first test script running on each devices and at some random scripts at times after that and it makes the test unreliable. What can be the problem?

[MJSONWP] Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: connect ECONNREFUSED 127.0.0.1:8200

Environment

  • Appium version (or git revision) that exhibits the issue: Appium 1.6.5 with UiAutomator2
  • Last Appium version that did not exhibit the issue (if applicable):
  • Desktop OS/version used to run Appium: Linux 3.10.0
  • Node.js version (unless using Appium.app|exe): 3.10.3
  • Mobile platform/version under test: Android 6.x, 7.x
  • Real device or emulator/simulator: Real device
  • Appium CLI or Appium.app|exe:

Details

While running uiautomator2 test scripts to multiple devices, the initial test script running on each device shows the following Appium error and test failed. Subsequent tests were executed OK after the initial failure or there were sporadic repro at random test scripts used with the same issue.

[MJSONWP] Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: connect ECONNREFUSED 127.0.0.1:8200

Appium log shows an error stating that platformName capability must be included, however the capability was already included as seen on the attached Appium log.

Link to Appium logs

appiumError-0.txt

appiumError-0-similar-but-slightly-different-log.txt

appium-0.txt

Capabilities used to create the uiautomator2 session

[MJSONWP] Calling AppiumDriver.createSession() with args: [null,null,[{"desiredCapabilities":{"appPackage":"com.pandora.android","appActivity":".Main","noReset":true,"newCommandTimeout":600,"automationName":"uiautomator2","platformName":"Android","deviceName":"Android Device"}},{"requiredCapabilities":{}}]]

@mykola-mokhnach mykola-mokhnach added the Android related to Android-native driver(s) label Jun 3, 2017
@Zenerax
Copy link
Author

Zenerax commented Jun 5, 2017

I tried assigning different unused ports for each test run using "systemPort" capability as a part of desired capability and it does not show the race condition.

#8535

@Zenerax Zenerax closed this as completed Jun 7, 2017
@mirro0707
Copy link

I encountered the same problem,I don't known what happened. It is ok after I restart the win platform's appium server with nodeconfig.

@menglihuakaij
Copy link

我并行执行也遇到了这个问题,,,请问有人解决的吗。

@lock
Copy link

lock bot commented Aug 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android related to Android-native driver(s)
Projects
None yet
Development

No branches or pull requests

4 participants