appium / appium/java-client

Getting Socket Hang Up error

Open
#1,430 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.3k
Forks
752
Avg merge
6d 21h
Merged PRs (30d)
8

Description

Description
I am trying to run multiple test cases using testng. But everytime after 4 or 5 test cases I am getting "[ERROR] An unknown server-side error occurred while processing the command. Original error: Could not proxy command to the remote server. Original error: socket hang up (WARNING: The server did not provide any stacktrace information
)"

Environment
Appium version (or git revision) that exhibits the issue: 1.18.0
Last Appium version that did not exhibit the issue (if applicable):
Desktop OS/version used to run Appium:10
Node.js version (unless using Appium.app|exe):v12.14.0
Npm or Yarn package manager:
Mobile platform/version under test:7.1.1
Real device or emulator/simulator: Real Device
Appium CLI or Appium.app|exe: Appium.exe

Code To Reproduce Issue [ Good To Have ]

Please remember: it's easier to reproduce and fix the bug with sample code.
You can git clone https://github.com/appium/appium/tree/master/sample-code or https://github.com/appium/appium/tree/master/sample-code/apps and reproduce an issue using Java and sample apps.
Also you can create a gist with pasted java code sample or put it here using markdown. About markdown please read Mastering markdown and
Writing on GitHub

Exception Stacktraces

https://gist.github.com/sudhanshuprakash/74e3c462e14db9f13f04ca29f5eb1049#file-appium-socket-hang-up

Link To Appium Logs

https://gist.github.com/sudhanshuprakash/5b7a0a57c3ead847e9767316262e8399#file-appium-logs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked exception stacktrace and Appium logs, then examine the reported Appium 1.18.0, Node.js v12.14.0, Windows 10, Android 7.1.1 real-device setup during repeated TestNG runs. Done means identifying a reproducible cause and confirming a fix or actionable diagnosis.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.