appium 🚀 - Update appium-android-driver to search for correct webview regex

@bootstraponline @jlipps ideas?

aluedeke on 25 Feb 2015

ok just figured out that i can set androidDeviceSocket to packagename_devtools_remote for my hybrid app in capablities and then its able to find it.

but now the chromdriver session cannot be created:

error: Chromedriver create session did not work. Status was 200 and body was {"sessionId":"1ba7c300de2460eb7387e107b1dbacc0","status":100,"value":{"message":"chrome not reachable\n  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Linux 3.13.0-46-generic x86_64)"}}
info: [debug] Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while processing the command. (Original error: Did not get session redirect from Chromedriver)","origValue":"Did not get session redirect from Chromedriver"},"sessionId":null}

aluedeke on 25 Feb 2015

ok and finally i figured out that the issue is one in chromedriver. its trying to connect to the wrong socket in android:

Sending adb command: host-serial:CB5122TKT3:forward:tcp:12509;localabstract:webview_devtools_remote_1186

unfortunately there is no way to convince chromedriver to connect to another socket.

aluedeke on 25 Feb 2015

interesting. @paymand how do you get around this with Opera?

jlipps on 25 Feb 2015

just as an update i modified chromedriver recompiled it and now it works. Will talk soon to the chromiumdriver developers how to resolve that properly

@paymand i was not able to get it running with the operaChromiumDriver would love to have a look into the source which is not public right?

aluedeke on 26 Feb 2015

The provided binary and examples found at https://github.com/operasoftware/operachromiumdriver are a bit outdated. I'll see if I can get someone to update them.

paymand on 7 Mar 2015

@paymand i just need to know if they changed the chromedriver to be actually able to find the right unix socket on the device? the current logic seems to be not able to connect to chromeview sockets. It that is the case i can open a ticket in chromedriver

aluedeke on 12 Mar 2015

@aluedeke: For Opera mobile (final/beta) we use our modified version of the chromedriver (aka operadriver) and the value I use for androidDeviceSocket cap is app_package + ".devtools".

paymand on 13 Mar 2015

@aluedeke: FYI, I've updated the docs/examples/executables for OperaDriver:
https://github.com/operasoftware/operachromiumdriver/releases

paymand on 24 Mar 2015

@aluedeke: I'm performing this issue now. What is your resolution for these days? Are you still using your patched version of chromedriver?

mpetrak on 28 Apr 2015

@mpetrak i did only a poc for a customer and didn't had time to investigate this further. i would bet the the issue is still there. Chromium code is still not updated.

Here is my patch:

diff --git a/chrome/test/chromedriver/chrome/device_manager.cc b/chrome/test/chromedriver/chrome/device_manager.cc
index 8e77f0c..00e60d8 100644
--- a/chrome/test/chromedriver/chrome/device_manager.cc
+++ b/chrome/test/chromedriver/chrome/device_manager.cc
@@ -124,18 +124,7 @@ Status Device::ForwardDevtoolsPort(const std::string& package,
                                    int port,
                                    std::string* device_socket) {
   if (device_socket->empty()) {
-    // Assume this is a WebView app.
-    int pid;
-    Status status = adb_->GetPidByName(serial_,
-                                       process.empty() ? package : process,
-                                       &pid);
-    if (status.IsError()) {
-      if (process.empty())
-        status.AddDetails(
-            "process name must be specified if not equal to package name");
-      return status;
-    }
-    *device_socket = base::StringPrintf("webview_devtools_remote_%d", pid);
+    *device_socket = package + "_devtools_remote";
   }

   return adb_->ForwardPort(serial_, port, *device_socket);
@@ -219,4 +208,3 @@ bool DeviceManager::IsDeviceLocked(const std::string& device_serial) {
   return std::find(active_devices_.begin(), active_devices_.end(),
                    device_serial) != active_devices_.end();
 }
-

aluedeke on 28 Apr 2015

@aluedeke Thank you for informations

mpetrak on 28 Apr 2015

Ok so this is a bug with the workaround. Putting it in new feature, we might have a go at it once most of the more urgent issues are sorted.

sebv on 3 Jun 2015

here's an open issue for this: crosswalk-project/crosswalk-web-driver#17

hypery2k on 16 Oct 2015

I'm using the Cordova Crosswalk plugin and also hitting this. Has there been any resolution on the Chromedriver side?

For what it's worth, here's a fuller Chromedriver patch that exposes androidDeviceSocket as a desired capability under chromeOptions.

This patch works w/ the current version of Appium. Swap in the patched Chromedriver and pass your androidDeviceSocket to Appium in your desiredCapabilities like so

{
  "platformName":"Android",
  "deviceName":"my device",
  "androidDeviceSocket":"my.package_devtools_remote",
  "chromeOptions": {
    "androidDeviceSocket":"my.package_devtools_remote
  }
}

The patch:

diff --git a/chrome/test/chromedriver/capabilities.cc b/chrome/test/chromedriver/capabilities.cc
index 5846479..67de230 100644
--- a/chrome/test/chromedriver/capabilities.cc
+++ b/chrome/test/chromedriver/capabilities.cc
@@ -424,6 +424,8 @@ Status ParseChromeOptions(
         base::Bind(&ParseString, &capabilities->android_package);
     parser_map["androidProcess"] =
         base::Bind(&ParseString, &capabilities->android_process);
+    parser_map["androidDeviceSocket"] =
+        base::Bind(&ParseString, &capabilities->android_device_socket);
     parser_map["androidUseRunningApp"] =
         base::Bind(&ParseBoolean, &capabilities->android_use_running_app);
     parser_map["args"] = base::Bind(&ParseSwitches);
diff --git a/chrome/test/chromedriver/capabilities.h b/chrome/test/chromedriver/capabilities.h
index 2f78fec..85ebc62 100644
--- a/chrome/test/chromedriver/capabilities.h
+++ b/chrome/test/chromedriver/capabilities.h
@@ -105,6 +105,8 @@ struct Capabilities {

   std::string android_process;

+  std::string android_device_socket;
+
   bool android_use_running_app;

   base::FilePath binary;
diff --git a/chrome/test/chromedriver/chrome/device_manager.cc b/chrome/test/chromedriver/chrome/device_manager.cc
index c8c9736..5c92957 100644
--- a/chrome/test/chromedriver/chrome/device_manager.cc
+++ b/chrome/test/chromedriver/chrome/device_manager.cc
@@ -34,6 +34,7 @@ Device::~Device() {
 Status Device::SetUp(const std::string& package,
                      const std::string& activity,
                      const std::string& process,
+                     const std::string& device_socket,
                      const std::string& args,
                      bool use_running_app,
                      int port) {
@@ -47,19 +48,19 @@ Status Device::SetUp(const std::string& package,

   std::string known_activity;
   std::string command_line_file;
-  std::string device_socket;
+  std::string known_device_socket = device_socket;
   std::string exec_name;
   if (package.compare("org.chromium.content_shell_apk") == 0) {
     // Chromium content shell.
     known_activity = ".ContentShellActivity";
-    device_socket = "content_shell_devtools_remote";
+    known_device_socket = "content_shell_devtools_remote";
     command_line_file = "/data/local/tmp/content-shell-command-line";
     exec_name = "content_shell";
   } else if (package.find("chrome") != std::string::npos &&
              package.find("webview") == std::string::npos) {
     // Chrome.
     known_activity = "com.google.android.apps.chrome.Main";
-    device_socket = "chrome_devtools_remote";
+    known_device_socket = "chrome_devtools_remote";
     command_line_file = kChromeCmdLineFileBeforeM33;
     exec_name = "chrome";
     status = adb_->SetDebugApp(serial_, package);
@@ -74,9 +75,10 @@ Status Device::SetUp(const std::string& package,

     if (!known_activity.empty()) {
       if (!activity.empty() ||
-          !process.empty())
+          !process.empty() ||
+          !device_socket.empty())
         return Status(kUnknownError, "known package " + package +
-                      " does not accept activity/process");
+                      " does not accept activity/process/device_socket");
     } else if (activity.empty()) {
       return Status(kUnknownError, "WebView apps require activity name");
     }
@@ -108,7 +110,7 @@ Status Device::SetUp(const std::string& package,

     active_package_ = package;
   }
-  this->ForwardDevtoolsPort(package, process, port, &device_socket);
+  this->ForwardDevtoolsPort(package, process, port, &known_device_socket);

   return status;
 }
diff --git a/chrome/test/chromedriver/chrome/device_manager.h b/chrome/test/chromedriver/chrome/device_manager.h
index d27aa50..6348ba6 100644
--- a/chrome/test/chromedriver/chrome/device_manager.h
+++ b/chrome/test/chromedriver/chrome/device_manager.h
@@ -25,6 +25,7 @@ class Device {
   Status SetUp(const std::string& package,
                const std::string& activity,
                const std::string& process,
+               const std::string& device_socket,
                const std::string& args,
                bool use_running_app,
                int port);
diff --git a/chrome/test/chromedriver/chrome_launcher.cc b/chrome/test/chromedriver/chrome_launcher.cc
index ca9d504..8b64565 100644
--- a/chrome/test/chromedriver/chrome_launcher.cc
+++ b/chrome/test/chromedriver/chrome_launcher.cc
@@ -476,6 +476,7 @@ Status LaunchAndroidChrome(
   status = device->SetUp(capabilities.android_package,
                          capabilities.android_activity,
                          capabilities.android_process,
+                         capabilities.android_device_socket,
                          switches.ToString(),
                          capabilities.android_use_running_app,
                          port);

TimHambourger on 22 Oct 2015

I think the "solution" is for appium to fork chromedriver until the issue is fixed upstream.

bootstraponline on 23 Oct 2015

@bootstraponline Are you still planning on forking chromedriver in the meantime? If you set up the fork, I can make the necessary changes.

mattfritz on 4 Nov 2015

I don't currently use appium at work so I'm not planning to fork
chromedriver. I still think it'd make sense for the appium devs to do so
though.

On Wed, Nov 4, 2015, 11:03 AM Matt Fritz [email protected] wrote:

@bootstraponline https://github.com/bootstraponline Are you still
planning on forking chromedriver in the meantime? If you set up the fork, I
can make the necessary changes.

—
Reply to this email directly or view it on GitHub
https://github.com/appium/appium/issues/4597#issuecomment-153810714.

bootstraponline on 4 Nov 2015

Alright, thanks @bootstraponline

@sebv What are your thoughts on a chromedriver fork?

mattfritz on 9 Nov 2015

Hey, I have been using Appium for a while with great success (thx for great work) on my hybrid apps.

Now I have had to implement XWalk project ( https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview ) and I'm not able anymore to see my WEBVIEW context within appium .

I'm working on windows developping in JAVA.

My issue seems looking like current issue (https://github.com/appium/appium/issues/4597) or this one https://github.com/crosswalk-project/crosswalk-web-driver/issues/17

Do you guys have any updates for me regarding that issue ? Can I help on investigation ?
This issue is clearly a show stopper for us as it will makes all our past work on Appium useless.

Even an "ugly" workaround is acceptable for the moment. Thx for support

aorfevre on 25 Nov 2015

Hi @aorfevre.

This works for me:

@aluedeke chromedriver patch provided in this conversation
set androidDeviceSocket: my.package_devtools_remote capability
set chromedriverExecutable: path/to/patched/driver capability

I haven't any updates if there is something better now....

mpetrak on 26 Nov 2015

Thx @mpetrak for your fast reply!
Can you share the compiled chromedriver.exe ? Or shall compile it myself ?

Also, if my package is called : com.my.app; I shall named androidDeviceSocket as : com.my.app_devtools_remote ? is it right ?

aorfevre on 26 Nov 2015

@aorfevre

I have compiled and patched chromedriver for OS X only now.

Yes, com.my.app_devtools_remote should be the right name. If not sure Start android emulator / device, open your app and run these commands:

adb shell
shell@android$ cat /proc/net/unix |grep devtools_remote

Than you can see the right name. See https://crosswalk-project.org/documentation/android/android_remote_debugging.html for details.

mpetrak on 26 Nov 2015

@aorfevre. Did you manage to compile the exe. If yes, could you share it. I'm still confused how to compile it myself.

madiska on 3 Dec 2015

@madiska. Yes, there's a steep learning curve on compiling chromedriver from source. It's part of the chromium repo and uses the same build system.

General instructions
http://dev.chromium.org/developers/how-tos/get-the-code

Like @mpetrak I've only compiled and patched chromedriver for OS X. Here's what worked for me. Windows instructions should be similar:

1) Get depot_tools
Clone w/ git and add cloned directory to your PATH:
https://chromium.googlesource.com/chromium/tools/depot_tools.git

2) Get Gyp.
This is what the Chromium team recommends for non-Linux builds. There's a newer tool called GN recommended for Linux that may also work for Windows. Only Gyp worked for me on OS X.
Clone w/ git, then run the setup.py file w/ python
Instructions
https://github.com/enginetrouble/gyp-getting-started#how-to-build
Repo
https://chromium.googlesource.com/external/gyp.git

3) Get chromium src.
Don’t use git - you miss required build files that way. Instead use the tools fetch and gclient provided in depot_tools. Follow instructions from the link below. NOTE: Downloading chromium src can take several hours!
http://dev.chromium.org/developers/how-tos/get-the-code

4) Build chromedriver. Continue following instructions from the dev.chromium.org link. Where it tells you to build the chrome target, build the chromedriver target instead. I.e.

ninja -C out/Release chromedriver

Other helpful links:
GYP options
https://www.chromium.org/developers/gyp-environment-variables

Good luck!

TimHambourger on 4 Dec 2015

@TimHambourger

Cheers. Actually I managed to get to some point, but then it was already 12 am. So I just went to bed. Took me a whole day to get all the stuff to work or not to throw errors. Hopefully building works.

madiska on 4 Dec 2015

hi @madiska & @TimHambourger ,
I'm facing big internet connexion issues and I still did not manage to clone Chromium repo.
Trying almost every night..

If @madiska you manage to build Windows Chrome version, I'll be glad to try it too.
In the meanwhile, I'll try again

aorfevre on 5 Dec 2015

@aorfevre & @TimHambourger

Sadly I'm unable to build it. It keeps getting stuck when I run the build command. No error message or anything. Google hasn't helped me also.

@aorfevre I'll keep trying but I think I won't be able to figure out what is causing this.

madiska on 5 Dec 2015

hi everybody,

a few weeks ago we investigated this question.
the main issue with _crosswalkwebdriver_ is - it uses xwalkOptions instead of chromeOptions in the desiredCapabilities object. so we patched appium to provide this object too.

i wrapped it to docker and you can use it on the windows pc too.

you can find code here - https://github.com/hamsterksu/appium-xwalk

sure you should specify androidDeviceSocket in your test. because xwalk uses different socket name than standard webview. and appium can't find it

according to driver path - you can specify it as run command parameter or from test too.

hamsterksu on 14 Dec 2015

@hamsterksu we could add this capability directly into appium.
if users supply a { automationName: 'crosswalk' } desired capability to appium, it can call crosswalkwebdriver and pass in these modified capabilities.

does that sound great?

Jonahss on 16 Dec 2015

@Jonahss cool, should be useful.

if you plan to add it to the framework maybe you can patch https://github.com/appium/appium/blob/master/lib/devices/android/android-hybrid.js
and use another algorithm to find crosswalk socket in this case? but it will not be completed solution because you need to use crosswalkwebdriver instead of chromewebdriver.

so i think you have 2 options

simple solution
- just add { automationName: 'crosswalk' }
- user(QA enginer) will specify androidDeviceSocket and chromedriverExecutable in test
complex solution
- add { automationName: 'crosswalk' }
- patch android-hybrid.js to find correct unix socket
- use crosswalkwebdriver instead of chromewebdriver
- version of crosswalkwebdriver should be configurable

i think option 2 is too complicated

what do you think?

hamsterksu on 16 Dec 2015

@Jonahss
Everything moving forward with crosswalk integration to Appium is welcome on my side.
Complex solution from @hamsterksu looks like the target. :)

mpetrak on 17 Dec 2015

Awesome work.
@hamsterksu's complex solution looks awesome. Appium 1.5's new architecture makes adding (and modifying) new drivers very easy. Forking appium-android-driver into a new module is pretty easy :) Then crosswalk can be added instead of chromedriver.

Right now, the main Appium contributors have a lot on their plate (getting 1.5 out, new Uiautomatior2 driver, new XCUITest driver) but this is something we'd like to see. Is anyone willing to work on this? We can provide guidance when it comes to the Appium codebase.

Jonahss on 17 Dec 2015

@Jonahss I can take a crack at it. Just to clarify:

Fork appium-android-driver to appium-crosswalk-driver and modify chromedriver references to reference crosswalkdriver. Allow different crosswalkdriver versions
Add crosswalk automationName config options to Appium
Modify android-hybrid.js to look for the Crosswalk unix socket and webview name

Anything else before I dig in?

mattfritz on 17 Dec 2015

@mattfritz my perspective is that it should not be a fork of appium-android-driver but a subclass of it (i.e., don't duplicate code across the packages). your other two points look right on to me!

jlipps on 17 Dec 2015

Hi @madiska & @aorfevre

Have you guys managed to build the chromedriver.exe?

ITKarel on 21 Dec 2015

@ITKarel I managed to build one, but not sure if it working. I will try to get it to work like Tim described and then upload the files, but first need to get it to work.

@TimHambourger Heia, Can you give us a working example how you used the new chromedriver. Some step seem to missing for me.

madiska on 22 Dec 2015

@mattfritz Did you make any progress on your "digging"?

I'm thinking of looking into it myself because the last comment is 2 weeks old. Let me know if you managed to get it working properly.

Would be nice to get a short response at least. Is a "fix" planned for this?

buekera on 6 Jan 2016

I was able to get it working with chromedriver. I had to patch chromedriver as well as android-hybrid.js For me using crosswalkwebdriver is not a viable solution as it has a dependency on docker to work on Windows.

ITKarel on 6 Jan 2016

@ITKarel What did you change in the android-hybrid.js and if you don't mind can you post the chromedriver somewhere.

madiska on 6 Jan 2016

@madiska I will post my complete solution a bit later today.

ITKarel on 7 Jan 2016

Thanks, @ITKarel ! That's awesome!

carolinasim on 8 Jan 2016

I added my rebuild chromedriver.exe as well as instructions on how to use. https://github.com/ITKarel/ChromeDriver

ITKarel on 11 Jan 2016

👍2

@ITKarel You are a lifesaver. Will try it out tommorow at work. :dancer:

madiska on 11 Jan 2016

Did you plan a Linux/Mac build? ;D

hypery2k on 11 Jan 2016

@chOOnz I took a look and the simple solution from @hamsterksu seems like the better option because crosswalkdriver released their binaries without naming conventions (e.g. the xwalk 16 driver). I haven't had time to work on it because of the holidays, but if you want to look at it and beat me to the punch that works too.

The complicated solution will probably not have a good way to specify a version, but going that direction would involve creating an Appium plugin for crosswalkdriver (like chromedriver) and integrating it into the android plugin.

I'l let you know if I have other updates later this week. Cheers!

mattfritz on 12 Jan 2016

Thanks a lot, @ITKarel ! This worked very well for me!

carolinasim on 13 Jan 2016

@hypery2k unfortunately I can only do a windows build. For Linux you can always try the xwalkdriver as suggested by @hamsterksu

ITKarel on 13 Jan 2016

@hamsterksu you mentioned that you wrapped crosswalkwebdriver to docker and you can use it on the windows pc too. Does this require docker to be installed on the PC?

ITKarel on 13 Jan 2016

@ITKarel Great work! Unfortunately I'm working on Linux, too, like @hypery2k
I will look into it within the next week and maybe I will be able to build the chromedriver for Linux/Mac. I will post here when I got any updates on that.

@mattfritz I didn't have any time either but I will look into it someday when I got some sparetime from actual work.

buekera on 14 Jan 2016

@ITKarel

Heya could you also upload the working appium setup example. I wanna see if I'm doing something wrong or there is another issue with the app. Currently I'm able to find the webview, but the tests don't do anything that.
So I'm wondering if I'm doing something wrong in the setup part.

Edit

I managed to get it to work. Thanks mate.

madiska on 15 Jan 2016

Hey guys, I'd really appreciate a chromedriver fix for a mac if you get a chance to build one or show me how to do it that'd be great too @chOOnz
@mattfritz any news on adding the fix to Appium? @TimHambourger would you be able to share your patched Chromedriver for Mac by any chance?

piotrekkmt on 20 Jan 2016

I am also stuck with a same issue and would like to know how to get the chromedriver fix for mac.
@piotrekkmt @chOOnz @TimHambourger

mayureshshirodkar on 28 Jan 2016

@mayureshshirodkar Here's a mac fix for the chromedriver version 2.20. Also added in the android-hybrid.js file and some how to steps for the chromeOptions capabilities.
https://github.com/piotrekkmt/chromedriver-appium

Thanks for listing out the steps @TimHambourger !

piotrekkmt on 1 Feb 2016

👍1

Thanks a lot @piotrekkmt @TimHambourger for the chromedriver. Works!

mayureshshirodkar on 1 Feb 2016

Thanks @piotrekkmt , works great!

souly1 on 19 Feb 2016

@jlipps @Jonahss i am not able to find android-hybrid.js file on Appium 1.5. Need to edit the androidHybrid.listWebviews method in ..\Appium\node_modulesappium\lib\devicesandroidandroid-hybrid.js to push {package name}_devtools_remote to the webviews list.

@piotrekkmt @souly1 @TimHambourger have you'll tried Crosswalk Apps on appium 1.5?

mayureshshirodkar on 26 Feb 2016

@piotrekkmt @souly1 @TimHambourger @jlipps @Jonahss

This fix doesn't work for me anymore since Appium 1.5. I don't know wether it's because of the missing android-hybrid.js or not.

Does anyone still use this workaround and got it working with Appium 1.5?

buekera on 9 Mar 2016

Sorry chOOnz, haven't tried 1.5from the notes of the release:
Appium 1.5 is a complete rewrite of Appium from the ground up.
1.4.16 is the latest version i worked with.

souly1 on 9 Mar 2016

@souly1 Thanks! I switched back to 1.4.16 in order to be able to modify the files I need to. I have no idea where the code went in 1.5. :D

I got a patched version of the chromedriver for linux which is working with crosswalk. Is anyone interested in using it?

buekera on 16 Mar 2016

yes, please
I'am interested in chromedriver for linux

didlich on 17 Mar 2016

@didlich Here you go: https://github.com/chOOnz/xwalk-chromedriver

Have fun with it! :-)

buekera on 17 Mar 2016

@chOOnz thanks

didlich on 17 Mar 2016

Hi there. I have gone here: https://github.com/piotrekkmt/chromedriver-appium and followed instructions (For Mac). I can now see the Web context:
["NATIVE_APP", "CHROMIUM"]

However, when I try to switch to chromium I get the following error in the server logs:

info: Chromedriver: Changed state to 'stopped'

error: Chromedriver: Chromedriver exited unexpectedly with code null, signal SIGTERM

warn: Chromedriver for context CHROMIUM stopped unexpectedly
warn: Chromedriver quit unexpectedly, but it wasn't the active context, ignoring

error: Chromedriver: Error: An error occurred (Original error: chrome not reachable
  (Driver info: chromedriver=2.18.343837 (52eb4041461e46a6b73308ebb19e85787ced4281),platform=Mac OS X 10.11.4 x86_64))
    at JWProxy.command$ (lib/proxy.js:149:15)
    at tryCatch (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at bound (domain.js:254:14)
    at GeneratorFunctionPrototype.runBound (domain.js:267:12)
    at run (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:89:39)
    at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-chromedriver/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:100:28
    at process._tickDomainCallback (node.js:381:11)
 { [Error: An error occurred (Original error: chrome not reachable
  (Driver info: chromedriver=2.18.343837 (52eb4041461e46a6b73308ebb19e85787ced4281),platform=Mac OS X 10.11.4 x86_64))]
  status: 100,
  value: { message: 'chrome not reachable\n  (Driver info: chromedriver=2.18.343837 (52eb4041461e46a6b73308ebb19e85787ced4281),platform=Mac OS X 10.11.4 x86_64)' },
  httpCode: 200 }

If I set the following:

'chromedriverExecutable' => '/usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver',

and rerun I get this error instead

Selenium::WebDriver::Error::UnknownError:
       Can't stop process; it's not currently running
error: Could not proxy command to remote server. Original error: connect ECONNREFUSED

info: --> GET /wd/hub/status {}
info: JSONWP Proxy: Proxying [GET /wd/hub/status] to [GET http://127.0.0.1:9515/wd/hub/status] with body: {}

info: [debug] Stopping logcat capture

Not sure what I might be doing wrong. Hoping someone can help as I am stuck with my Android automation until I can resolve this.

Thanks in advance.

danqa on 30 Mar 2016

Try and replace your appium-hybrid.js file, with the one @ITKarel has provided. See if it works.

mayureshshirodkar on 30 Mar 2016

@mayureshshirodkar no luck. I replaced it but still getting the same error. :(

danqa on 30 Mar 2016

@danqa which Appium version are you using? The chromedriver fix on my github works with the latest 1.4 version. But on 1.5 the appium-hybrid.js doesn't do the trick and that seems like your problem. The context displayed is Chromium instead of the webview inside of it.

Was anyone able to find where did the context handling for hybrid apps in appium-hybrid.js go in 1.5?
On the other hand, is there a different fix (less hacky) for hybrid apps based on Crosswalk?

peterpoliwoda on 31 Mar 2016

@peterpoliwoda I am using 1.4.16. I updated the appium-hydrid.js and dowloaded the latest version of chromdriver but see CHROMIUM not WebView. Can you point me to your chromedriver fix?

danqa on 31 Mar 2016

Update: I cleaned out appium from my machine and reinstall version 1.4.16 via npm. I then followed all the information on @peterpoliwoda github for the fix.

When I run I now see 2 contexts:
["NATIVE_APP", "WEBVIEW_com.my.app_devtools_remote"]

So I do:
driver.set_context('WEBVIEW_com.my.app_devtools_remote')

But at that point the system hangs. I see the following in the logs:

info: Chromedriver: [STDOUT] Starting ChromeDriver 2.20.370386 (91c49fb9369f1323d7022402d86aac62b4244cb4) on port 9515 Only local connections are allowed. info: JSONWP Proxy: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body info: JSONWP Proxy: Got response with status 200: "{\"sessionId\":\"\",\"status\":0,\"value\":{\"build\":{\"version\":\"alpha\"},\"os\":{\"arch\":\"x86_64\",\"name\":\"Mac OS X\",\"version\":\"10.11.4\"}}}" info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.my.app","androidUseRunningApp":true,"androidDeviceSerial":"192.199.199.101:5555"}}} info: [debug] Didn't get a new command in 60 secs, shutting down... info: Shutting down appium session info: [debug] Pressing the HOME button

I have no waits in my code so I am not sure why its not working.

danqa on 31 Mar 2016

@danqa can you please try with appium 1.5.1 the latest ..

saikrishna321 on 1 Apr 2016

@saikrishna321

with version 1.5.1 it finds the CHROMIUM webview but when I try to switch to it it hangs then fails:

[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","CHROMIUM"] [debug] [AndroidDriver] Connecting to chrome-backed webview context 'CHROMIUM' [debug] [Chromedriver] Changed state to 'starting' [Chromedriver] Set chromedriver binary as: /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver [Chromedriver] Killing any old chromedrivers, running: ps -ef | grep /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver | grep -v grep |grep -e '--port=9515$\s.*$\?$' | awk '{ print $2 }' | xargs kill -15 [Chromedriver] Successfully cleaned up old chromedrivers [Chromedriver] Spawning chromedriver with: /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver --url-base=wd/hub --port=9515 --adb-port=5037 [Chromedriver] [STDOUT] Starting ChromeDriver 2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4) on port 9515 Only local connections are allowed. [JSONWP Proxy] Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body [JSONWP Proxy] Got response with status 200: "{\"sessionId\":\"\",\"status\":0,\"value\":{\"build\":{\"version\":\"alpha\"},\"os\":{\"arch\":\"x86_64\",\"name\":\"Mac OS X\",\"version\":\"10.11.4\"}}}" [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.my.app","androidUseRunningApp":true,"androidDeviceSerial":"192.168.99.101:5555"}}} [JSONWP Proxy] Got response with status 200: {"sessionId":"16581f2900fd227d1985aa5d2c9d5bdd","status":100,"value":{"message":"chrome not reachable\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=M... [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.my.app","androidUseRunningApp":true,"androidDeviceSerial":"192.168.99.101:5555"}}} [JSONWP Proxy] Got response with status 200: {"sessionId":"a03f1a6212923daf9894649a753d2b64","status":100,"value":{"message":"chrome not reachable\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=M... [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.my.app","androidUseRunningApp":true,"androidDeviceSerial":"192.168.99.101:5555"}}} [JSONWP Proxy] Got response with status 200: {"sessionId":"b5af6a6a03939bc5ee4e92a39742c129","status":100,"value":{"message":"chrome not reachable\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=M... [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.my.app","androidUseRunningApp":true,"androidDeviceSerial":"192.168.99.101:5555"}}} [JSONWP Proxy] Got response with status 200: {"sessionId":"6a0e6860696383c08bb0dfb32b1030bb","status":100,"value":{"message":"chrome not reachable\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=M... [Chromedriver] Chromedriver exited unexpectedly with code null, signal SIGTERM [debug] [Chromedriver] Changed state to 'stopped' [Chromedriver] Error: An error occurred (Original error: chrome not reachable (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Mac OS X 10.11.4 x86_64)) at JWProxy.command$ (lib/proxy.js:139:15) at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21) at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37) at run (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:104:47) at /usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:115:28 at flush (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/$.microtask.js:19:5) at nextTickCallbackWith0Args (node.js:415:9) at process._tickCallback (node.js:344:13) { [Error: An error occurred (Original error: chrome not reachable (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Mac OS X 10.11.4 x86_64))] status: 100, value: { message: 'chrome not reachable\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Mac OS X 10.11.4 x86_64)' }, httpCode: 200 } [MJSONWP] Encountered internal error running command: Error: An error occurred (Original error: chrome not reachable (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Mac OS X 10.11.4 x86_64)) at JWProxy.command$ (lib/proxy.js:139:15) at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21) at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37) at run (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:104:47) at /usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:115:28 at flush (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/$.microtask.js:19:5) at nextTickCallbackWith0Args (node.js:415:9) at process._tickCallback (node.js:344:13) [HTTP] <-- POST /wd/hub/session/67411f3f-4c17-4184-b0f9-48c9d99d7657/context 500 241883 ms - 346

Still stuck. Works fine for all my iOS stuff.

danqa on 1 Apr 2016

@imurchie can you please on this

saikrishna321 on 1 Apr 2016

Anyone have any ideas? I'm stuck at this point in my android development for automation.

danqa on 4 Apr 2016

*_EDIT *_*
Even if I don't get why, but my tests are now running after adding this desiredCapability : autoWebview = true

Dear all,

Has someone tried docker provided by @hamsterksu ???

I working on Windows for dev and for Continous integration, we do have Linux servers so Docker solution is a must for us.
I develop my e2e tests on JUnit.

What is working :

docker is running on windows
phone is accessible from docker
app is installed on device remotly
I see more context now, NATIVE_APP and CHROMIUM.

I was expecting a WEBVIEW context.

Now my issue is that I can't find also any element from my webview.

*_Does anyone has an idea or suggestion ? *_

Here my config

String appLoc = "/home/apks/";
String appName = "android-armv7-debug.apk";
String myPackage = "com.mypackage";
String appiumUri = "http://192.168.99.100:4723/wd/hub";


DesiredCapabilities capabilities = new DesiredCapabilities();

capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "Android");
capabilities.setCapability("platformVersion", "4.4.2");
capabilities.setCapability("app", appLoc+appName);
capabilities.setCapability(MobileCapabilityType.APP_PACKAGE,myPackage);
capabilities.setCapability(MobileCapabilityType.TAKES_SCREENSHOT,"true");
capabilities.setCapability(MobileCapabilityType.NEW_COMMAND_TIMEOUT,15);

// for xwalk socket
capabilities.setCapability("androidDeviceSocket",myPackage+"_devtools_remote");

driver = new AndroidDriver<>(new URL(appiumUri), capabilities);

I access to element with xpath locators. Element is visible when error occurs

public static By getAgreementsBtn () {
    return By.xpath("//button[@ng-click='termOfUseToogle()']") ;
}

Tests in error:
  test.java.com.rizze.citizzeye.AuthenticationWebViewTest: An element could not be located on the page using the given search parameters. (WARNING: The server did not provide any stacktrace informatio
n)(..)

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0

thank everyone for support

aorfevre on 19 Apr 2016

Has there been any progress on this? I upgraded to Appium 1.5.2 which shows in the change logs support for chrome browser but it still is not allowing a switch the the Chromium web view. Any help greatly appreciated.

danqa on 3 May 2016

Is there a way to run Appium with NOT PATCHED Chromedriver to test crosswalk-based application? I've tried Appium 1.5.2 with no success (_{"message":"chrome not reachable\n (Driver info: chromedriver=2.21.371461 ...}_) after correct switching to CHROMIUM context. androidDeviceSocket was set correctly.

It is important to me to webdriver be not patched, since such driver cannot be used for remote testing in cloud services like SauceLabs. Thanks in advance for reactions.

petrmiko on 4 May 2016

As far as I know there has been no movement on this. 1.5.2 supports chrome and chromium, but only through the stock ChromeDriver (version 2.2.1).

The only issue I can find in ChromeDriver is https://bugs.chromium.org/p/chromedriver/issues/detail?id=749 if you'd like to get on there and try to get some interest going.

imurchie on 4 May 2016

Thanks for pointing out the ChromeDriver issue, writing there is the least I can try.

petrmiko on 5 May 2016

I am on 1.5.2 with Appium Java Client 4.0.0. This issue still persists on an Android App with Webview for Facebook, Twitter & Gmail authentications. Appium is not able to find the webviews (doesn't list the context) on both emulator and real device.

kskrishnan on 1 Jun 2016

@kskrishnan is your app built with CrossWalk?

imurchie on 1 Jun 2016

@chOOnz is it possible for you to re-upload the linux xwalk webdriver ? thanks for helping btw

outEduardoSilva on 14 Jun 2016

Update (24 Jun, 2016):
latest patch version can be found on https://github.com/rokkknrollla/appium-android-xwalk-driver-patch

Hi everyone! Based on this solution: https://github.com/piotrekkmt/chromedriver-appium - I managed to patch Appium 1.5.3 (with Appium Java Client 4.0.0) so it now can recognize Cordova (CrossWalk) WebViews on macOS

I guess this patch would work with any other OS as well but you'll need chromedriver binary for that OS (i.e. Windows: https://github.com/ITKarel/ChromeDriver)

The steps as follows:

Install Appium 1.5.3 via NPM

$ npm install -g appium

Patch appium-android-driver

$ cd /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/
$ patch -p1 lib/webview-helpers.js /path/to/patch/file/webview_helpers_cordova_suppport.patch

Rebuild Appium Android Driver (run command in module root directory)

$ npm install

Copy patched ChromeDriver into module directory

$ cd /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/
$ cp -i /path/to/patched/file/chromedriver .
overwrite ./chromedriver? (y/n [n]) y

Start Appium as usual

$ appium
[Appium] Welcome to Appium v1.5.3 (REV 02ccb7dcfd188d33795d19a2846c937c93851ff8)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723

Add capabilities as follows

String ANDROID_APP_PACKAGE = "com.example.app.package";
String ANDROID_DEVICE_SOCKET = ANDROID_APP_PACKAGE + "_devtools_remote";
capabilities.setCapability("androidDeviceSocket", ANDROID_DEVICE_SOCKET);
ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.setExperimentalOption("androidDeviceSocket", ANDROID_DEVICE_SOCKET);
capabilities.setCapability(ChromeOptions.CAPABILITY, chromeOptions);