question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Could not proxy

See original GitHub issue

The problem

I get an error “Top level suite × Non-spec failure - WebDriverError: An unknown server-side error occurred while processing the command. Original error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: Error: ESOCKETTIMEDOUT” when running simple test for Hybrid application on real Android device

Environment

  • Appium version (or git revision): 1.7.1
  • Desktop OS/version used to run Appium: Win 8x64
  • Node.js version: 6.9.2
  • Npm version: 3.10.9
  • Mobile platform/version under test: Android 7.1.1
  • Real device or emulator/simulator: Real device, Nexus 9
  • Appium CLI or Appium.app|exe: Appium Desktop
  • framework: ‘jasmine2’

Details

The application is installed on a real device. Tests simply start the application, check the presence of the element. Then you receive an error message. I found https://github.com/appium/appium/issues/7063 but I still don’t know how to solve the problem.

Link to Appium logs

https://gist.github.com/JanePes/733d5bbe34c49975ef2210d10621dc45

Code To Reproduce Issue [ Good To Have ]

Part of ‘config.js’:

beforeLaunch: function () {
      return new Promise(function (resolve) {
          reporter.beforeLaunch(resolve);

          if (fs.existsSync('jasmine-results.json.lock')) {
              fs.unlinkSync('jasmine-results.json.lock');
          }
          if (fs.existsSync('jasmine-results.json')) {
              fs.unlink('jasmine-results.json');
          }
      });
  },
  onPrepare: function () {

      wdBridge.initFromProtractor(exports.config);
      jasmine.getEnv().addReporter(reporter);
      var SpecReporter = require('jasmine-spec-reporter').SpecReporter;
      jasmine.getEnv().addReporter(new SpecReporter({displayStacktrace: 'all'}));

      browser.ignoreSynchronization = true;
  },

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:14

github_iconTop GitHub Comments

3reactions
JanePescommented, Dec 21, 2017

I found a solution. I added

nativeWebScreenshot: true,
androidScreenshotPath: 'target/screenshots',

in capabilities and now all works fine

1reaction
jenhbocommented, Feb 21, 2019

I use browserstack to run all scripts, my scripts failed at the same issue, no ways to add the parameters. are there any other solutions ?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Could not proxy request /pusher/auth from localhost:3000 to ...
I am trying to create a chat app using reactJS and pusher, i am getting this error-. Could ...
Read more >
Could not proxy request [route] from localhost:3000 to ... - Reddit
This error is very general and all the online help I see is just like "Make sure the server is on" etc, which...
Read more >
Could not proxy request /config from localhost:3000 ... - GitHub
I'm trying to run the mozaik2 demo locally on my Mac with npm installed thru homebrew. It launches the browser window but then...
Read more >
Ronan_Morgan - MongoDB
Proxy Error: Could not proxy request /api/calendar/create-event from localhost:3000 to http://127.0.0.1:5000/. (ECONNRESET).
Read more >
Proxy error ECONNREFUSED when using daml-ui-template
Proxy error: Could not proxy request /v1/exercise from localhost:3000 to http://localhost:7575. See https://nodejs.org/api/errors.html# ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found