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.

Appium 1.7.1 issue with chrome session on real device

See original GitHub issue

The problem

The Chrome browser opens and not responding and stays still

[debug] [JSONWP Proxy] Got response with status 200: "{\"sessionId\":\"\",\"status\":0,\"value\":{\"build\":{\"version\":\"alpha\"},\"os\":{\"arch\":\"x86_64\",\"name\":\"Windows NT\",\"version\":\"10.0.15063\"}}}"
[debug] [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.android.chrome","androidDeviceSerial":"a2573096"}}}
[debug] [Chromedriver] Webview version: 'Chrome/61.0.3163.98'

and then throws the following error:

[Chromedriver] Chromedriver exited unexpectedly with code null, signal SIGTERM
[debug] [Chromedriver] Changed state to 'stopped'
[Chromedriver] Error: unknown error: Device axxxxx is already in use

Environment

Appium version (or git revision) that exhibits the issue:1.7.1
Last Appium version that did not exhibit the issue (if applicable):
Desktop OS/version used to run Appium:Windows
Node.js version (unless using Appium.app|exe):v8.9.0
Mobile platform/version under test: Android 6.0.1/ Chrome/61.0.3163.98
Real device or emulator/simulator: real device
Appium CLI or Appium.app|exe:

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

https://gist.github.com/automation311/617c31456e924ea70c15059c6ffdbb34

Code To Reproduce Issue [ Good To Have ]

   @Test
        public void test() throws MalformedURLException, InterruptedException {
              AppiumDriver driver;

            DesiredCapabilities capabilities = DesiredCapabilities.android();

            capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, BrowserType.CHROME);

            capabilities.setCapability(MobileCapabilityType.PLATFORM, Platform.ANDROID);

            capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME , "Android");

             capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "my phone");

             capabilities.setCapability (MobileCapabilityType.VERSION, "6.0.1");

            URL url = new URL("http://0.0.0.0:4723/wd/hub");

            driver = new AndroidDriver(url,capabilities);
}

Issue Analytics

State:
Created 6 years ago
Comments:28 (13 by maintainers)

Top GitHub Comments

1reaction

automation311commented, Nov 9, 2017

Got it. Thanks. now i have chromedriver 2.33. when i run my test it shows started 2.33.

0reactions

lock[bot]commented, Sep 4, 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.

Top Results From Across the Web

Appium 1.7.1 issue with chrome session on real device -

Appium 1.7.1 issue with chrome session on real device. ... The problem. The Chrome browser opens and not responding and stays still

Appium 1.7.0 Released - News

Known Issues: Android. Webviews on Android O do not work because of a bug in Chromedriver. We are working on a workaround. Chrome...

[Appium Error] : could not find devices - Google Groups

first check android sdk and JAVA is properly installed or not.. then check your PATH... don't remove the older path, just edit that...

Un able to execute Appium script on real Device

Updated the device name in script and updated browser as "Chrome" Executed Script -> The browser opens up -->. Issues: It always prompts...

Appium python client - Gitter

Original error: Error: socket hang up". Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device- ...