Java-client version 3.2.0 released

VikramVI · September 15, 2015, 8:58am

Congratulations on one more successful release. Great job guys Sergey and Jonahss.

Best Regards,
Vikram

Raman · September 24, 2015, 3:10pm

This is an Awesome update.Great Job Team !!!

I just tried the new 3.2 and the appium server works absolutely fine without any issues. I have recorded a tutorial on the same if anyone needs step by step information can go through the youtube video from below link:

Thanks,
Raman
http://www.way2automation.com

SergeyTichomirov · September 28, 2015, 11:52am

This is the good work

I’m also going to add some new samples here

SergeyTichomirov · September 29, 2015, 7:26am

Here is a PR with sample update:

I hope it will help you to add new chapters to your tutorial

sunny_sachdeva · October 6, 2015, 11:16am

HI All,

I have upgraded my Appium from 1.4.8 to 1.4.12. Can any one help in launching appium programatically in MAC , enabling developer setting so that AppiumJS package points to the new build.

Thanks
Sunny

hemche · October 6, 2015, 11:23am

Check this thread.

SergeyTichomirov · October 6, 2015, 12:02pm

There is one more interesting conversation

rakesh · October 26, 2015, 2:44pm

Any help would be appropriated

I need to click or tap on Go/Done button on android s3 device which running 4.3 version

I tried all sorts of option

driver.pressKeyEvent(66) or driver.pressKeyEvent(AndroidKeyCode.ENTER)
Driver.sendKeyEvent(66)
driver.execute(“mobile:keyevent”, “keycode:66”);

I manage to click on all keys except Go/Done button

Environments
Appium version - 1.4.13
Java 1.7 appium
Maven dependency - 3.2.0

Sandeep_Teja_Mummoji · October 28, 2015, 12:52pm

I am trying to execute the following code on “Ubuntu” but unable to execute it, getting error as below.

import java.io.File;
import java.net.URL;
import java.util.concurrent.TimeUnit;

import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.Test;

import io.appium.java_client.MobileElement;
import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.remote.MobileCapabilityType;
import io.appium.java_client.remote.MobilePlatform;
import io.appium.java_client.service.local.AppiumDriverLocalService;
import io.appium.java_client.service.local.AppiumServiceBuilder;

public class TestLatestAppiumVersion {

public static AndroidDriver<MobileElement> driver;

@Test
public void testServer() throws Exception {

    File classpathRoot = new File(System.getProperty("user.dir"));
    System.out.println(classpathRoot);
    File app = new File(classpathRoot, "whatsapp.apk");

    AppiumDriverLocalService service = AppiumDriverLocalService.buildService(new AppiumServiceBuilder()
            .usingDriverExecutable(new File("/home/xxx/.linuxbrew/Cellar/node/4.2.1/bin/node"))
            .withAppiumJS(new File("/home/xxx/.linuxbrew/lib/node_modules/appium/bin/appium.js"))
            .withLogFile(new File("/home/xxx/workspace/xxx/log.txt")));

    System.out.println("Requesting to start server");
    service.start();
    System.out.println("Server has started!!!");

    DesiredCapabilities capabilities = new DesiredCapabilities();
    capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "MyVirtualDevice");
    capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, MobilePlatform.ANDROID);
    capabilities.setCapability(MobileCapabilityType.BROWSER_NAME, "");
    capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION, "5.0");
    capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME, "Appium");
    capabilities.setCapability(MobileCapabilityType.APP, app.getAbsolutePath());

    driver = new AndroidDriver<MobileElement>(new URL("http://127.0.1.1:4723/wd/hub"), capabilities);
    driver.manage().timeouts().implicitlyWait(20L, TimeUnit.SECONDS);

    driver.quit();
    service.stop();
    System.out.println("Server has stopped successfully!!!");
}

}

OUTPUT:

2015-10-28 12:44:38:266 - info: Welcome to Appium v1.4.13 (REV c75d8adcb66a75818a542fe1891a34260c21f76a)
2015-10-28 12:44:38:268 - info: Appium REST http interface listener started on 0.0.0.0:4723
2015-10-28 12:44:38:271 - info: [debug] Non-default server args: {“log”:"/home/grabhouse/workspace/Grabhouse/log.txt"}
2015-10-28 12:44:38:271 - info: Console LogLevel: debug
2015-10-28 12:44:38:271 - info: File LogLevel: debug
2015-10-28 12:44:38:529 - info: --> GET /wd/hub/status {}
2015-10-28 12:44:38:531 - info: [debug] Responding to client with success: {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“c75d8adcb66a75818a542fe1891a34260c21f76a”}}}
2015-10-28 12:44:38:537 - info: <-- GET /wd/hub/status 200 7.669 ms - 105 {“status”:0,“value”:{“build”:{“version”:“1.4.13”,“revision”:“c75d8adcb66a75818a542fe1891a34260c21f76a”}}}
2015-10-28 12:44:38:915 - info: --> POST /wd/hub/session {“desiredCapabilities”:{“automationName”:“Appium”,“platformVersion”:“5.0”,“app”:"/home/grabhouse/workspace/Grabhouse/whatsapp.apk",“deviceName”:“MyVirtualDevice”,“platformName”:“Android”,“browserName”:""}}
2015-10-28 12:44:38:916 - info: Client User-Agent string: Apache-HttpClient/4.3.3 (java 1.5)
2015-10-28 12:44:38:919 - info: [debug] No appActivity desired capability or server param. Parsing from apk.
2015-10-28 12:44:38:919 - info: [debug] No appPackage desired capability or server param. Parsing from apk.
2015-10-28 12:44:38:920 - info: [debug] Using local app from desired caps: /home/grabhouse/workspace/Grabhouse/whatsapp.apk
2015-10-28 12:44:38:921 - info: [debug] Creating new appium session 4bacfd6b-b7c6-42fe-996c-147689cc2e7c
2015-10-28 12:44:38:921 - info: Starting android appium
2015-10-28 12:44:38:923 - info: [debug] Getting Java version
2015-10-28 12:44:38:969 - info: Java version is: 1.7.0_79
2015-10-28 12:44:38:971 - info: [debug] Checking whether adb is present
2015-10-28 12:44:38:971 - warn: The ANDROID_HOME environment variable is not set to the Android SDK root directory path. ANDROID_HOME is required for compatibility with SDK 23+. Checking along PATH for adb.
2015-10-28 12:44:38:971 - info: [debug] executing cmd: which adb
2015-10-28 12:44:38:976 - info: [debug] Cleaning up android objects
2015-10-28 12:44:38:976 - info: [debug] Cleaning up appium session
2015-10-28 12:44:38:977 - error: Failed to start an Appium session, err was: Error: Could not find adb. Please set the ANDROID_HOME environment variable with the Android SDK root directory path.
2015-10-28 12:44:38:979 - info: [debug] Error: Could not find adb. Please set the ANDROID_HOME environment variable with the Android SDK root directory path.
at [object Object]. (/home/grabhouse/.linuxbrew/lib/node_modules/appium/node_modules/appium-adb/lib/adb.js:126:12)
at ChildProcess.exithandler (child_process.js:210:5)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:818:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
2015-10-28 12:44:38:979 - info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Could not find adb. Please set the ANDROID_HOME environment variable with the Android SDK root directory path.)”,“origValue”:“Could not find adb. Please set the ANDROID_HOME environment variable with the Android SDK root directory path.”},“sessionId”:null}
2015-10-28 12:44:38:982 - info: <-- POST /wd/hub/session 500 67.119 ms - 342.

I had set the Environment variables in “~/.bashrc”,"~/.profile" & also “~/.bash_profile” as follows:

export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export PATH=$JAVA_HOME/bin:$PATH

export MAVEN_HOME=/home/grabhouse/Documents/apache-maven-3.3.3
export PATH=$MAVEN_HOME/bin:$PATH

export ANDROID_HOME=/home/grabhouse/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/platform-tools/
export PATH=$PATH:$ANDROID_HOME/tools/
export PATH=$PATH:$ANDROID_HOME/build-tools/

and also tried with,

export ANDROID_HOME=/home/grabhouse/Android/Sdk
export PATH=$ANDROID_HOME/platform-tools:$PATH
export PATH=$ANDROID_HOME/tools:$PATH
export PATH=$ANDROID_HOME/build-tools:$PATH

Also unable to install GUI version of “Appium on Ubuntu”, unable to open "uiautomatorviewer"

Help me in this regard,
Thanks in advance
Sandeep.

Priyank_Shah · October 28, 2015, 3:34pm

Hi Sandeep,
are you able to run adb command manually from terminal? because i m also using ubuntu but did not face this issue. But i m running appium direct from source.
And related to GUI version, this is not meant for Windows and Mac…
Ubuntu user do not have this luxury :).

Thanks,
Priyank Shah

Sandeep_Teja_Mummoji · October 29, 2015, 6:12am

Thanks for the reply,
i have tried by running appium server from command line, it is running fine, but the latest release of appium 3.2 has got new feature to start the appium server from code. It is not working in that way.

pr4bh4sh · October 29, 2015, 6:25am

Use the latest java client code from git, the issue has been logged and resolved. This issue is with Nix based system when using eclipse.

Sandeep_Teja_Mummoji · October 29, 2015, 6:56am

Thanks for the reply,
Can you please let me know how to use the latest java client code from git? i am using maven to get the latest java client.

Priyank_Shah · October 29, 2015, 10:43am

You need to clone git project , and build locally. After that you can add java client jar to your project.

Sandeep_Teja_Mummoji · November 3, 2015, 5:54am

Can you please tell me, how to build it locally & add the java client jar to your project?

I had cloned the code from git, but i not aware of how to build it locally.
I had already added the latest appium jar into the project.

Thanks in advance,
sandeep.

SergeyTichomirov · November 18, 2015, 8:00pm

I think the new build will be published after the merging of this PR:

Venkatesh · November 19, 2015, 7:51am

Hi All,
Has somebody tried starting Appium server on mac using java client 3.2.0, if yes please share code.

Regards,
Venkatesh

SergeyTichomirov · November 19, 2015, 9:20am

This issue was fixed

github.com/appium/java-client

Unable to run Appium server programmatically

opened 05:28AM - 01 Oct 15 UTC

closed 04:18PM - 08 Oct 15 UTC

saikrishna321

bug Needs investigation Mac OS X

@TikhomirovSergey as you suggested in the previous post i have my node set in M…ac OSX path ➜ AppiumParallel git:(master) ✗ node --version v0.12.7 echo $PATH /Users/saikrisv/Library/Android/sdk/platform-tools:/Users/saikrisv/Library/Android/sdk/tools:/Users/saikrisv/Library/Android/sdk/platform-tools:/Users/saikrisv/Library/Android/sdk/tools:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin I able to run node command from any path from ma commandline. Below is the code i use to start the server AppiumServiceBuilder builder = new AppiumServiceBuilder().withAppiumJS(new File("/usr/local/lib/node_modules/appium/bin/appium.js")) .withArgument(GeneralServerFlag.APP, System.getProperty("user.dir") + "/build/wordpress.apk") .withArgument(GeneralServerFlag.LOG_LEVEL, "info").usingAnyFreePort(); /_and so on_/; AppiumDriverLocalService service = builder.build(); service.start(); Error ::: io.appium.java_client.service.local.InvalidNodeJSInstance: Node.js is not installed at io.appium.java_client.service.local.AppiumServiceBuilder.validateNodeJSVersion(AppiumServiceBuilder.java:87) at io.appium.java_client.service.local.AppiumServiceBuilder.findDefaultExecutable(AppiumServiceBuilder.java:137) at org.openqa.selenium.remote.service.DriverService$Builder.build(DriverService.java:290) at com.appium.android.test.AndriodTest.setUp(AndriodTest.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) Caused by: java.io.IOException: Cannot run program "node": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:450) at java.lang.Runtime.exec(Runtime.java:347) at io.appium.java_client.service.local.AppiumServiceBuilder.validateNodeJSVersion(AppiumServiceBuilder.java:83) ... 27 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 31 more java.lang.NullPointerException at com.appium.android.test.AndriodTest.tearDown(AndriodTest.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)

As a workaround I advice to use IDEA instead of Eclipse or set environmental variable in Eclipse. How to do it? This is described it the mentioned issue.

SergeyTichomirov · November 27, 2015, 9:32am

There are two fixes which are coming out with new a java_client version

The main problem was the way how Eclipse for UNIX-like OS’s works with environment variables. Else there was a problem with the starting of non-default Node.JS (e.g. NSolid)

Also there are enhancements: