Exception after Selenium 2.42.0 release about java-client HOT 13 CLOSED

Oh boy oh boy. I'll see what's up.

from java-client.

There is also an issue with switching contexts when having 2.42.0 as a dependency.

Running the AndroidWebViewTest.java sample results in the following error (which is all client-side, no server logs):

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Build info: version: '2.42.0', revision: '5e824302019c86eae9c8c3ca9155e7307b410cf8', time: '2014-05-24 09:48:41'
System info: host: 'isaac.local', ip: '10.35.4.58', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.2', java.version: '1.7.0_45'
Driver info: driver.version: AppiumDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:590)
    at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:81)
    at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:92)
    at io.appium.java_client.AppiumDriver.getContextHandles(AppiumDriver.java:493)
    at com.saucelabs.appium.AndroidWebViewTest.webView(AndroidWebViewTest.java:43)
        ...

Downgrading to 2.41.0 solves it.

from java-client.

Hmm, I updated the maven dependency and all tests still passing.

What code did you run to trigger this error?

from java-client.

The Appium sample code AndroidWebviewTest.java. In the pom.xml file, it consistently fails if I use

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>LATEST</version>
  <scope>test</scope>
</dependency>

If I change it, it works:

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>2.41.0</version>
  <scope>test</scope>
</dependency>

Running, from appium/sample-code/examples/java/junit,

mvn -Dtest=com.saucelabs.appium.AndroidWebViewTest test

from java-client.

Thanks. Will keep working on this.

from java-client.

Okay, working on an update to java-client.

from java-client.

It's confirmed as Selenium bug. Endpoints for contexts were accidentally deleted. Working on a PR to Selenium

from java-client.

here we are. I found this issue just now..

from java-client.

Looks like selenium will do a java release tomorrow.

from java-client.

Working on a new release of java-client.
Plus @pkastner's original issue will be resolved by some dependency refactoring I've done.

from java-client.

Released as 1.3.0, should fix.

Reopen if still having issues.

from java-client.

Thanks for the great work 👍

from java-client.

yay!

from java-client.