An unknown server-side error occurred while processing the command

Hi,

I am trying to automate an android app using Appium(1.3 beta). I am stuck in a very simple scenario. When the Login page opens, I am just trying to write username in user name field. The user name field can also be located in appium inspector. But it is not able to write in that field and showing up below error log.

ERROR LOG***
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 10.19 seconds
Build info: version: ‘2.44.0’, revision: ‘76d78cf’, time: ‘2014-10-23 20:02:37’
System info: host: ‘N/A’, ip: ‘N/A’, os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘10.9.5’, java.version: ‘1.7.0_67’
Session ID: 32382d44-67af-494a-8da1-75701c74b9d1
Driver info: io.appium.java_client.AppiumDriver
Capabilities [{platform=MAC, javascriptEnabled=true, appActivity=com.salesforce.chatter.Chatter, browserName=Android, networkConnectionEnabled=true, desired={platform=MAC, platformName=Android, deviceName=Android, appActivity=com.salesforce.chatter.Chatter, appPackage=com.salesforce.chatter, version=4.4}, locationContextEnabled=false, appPackage=com.salesforce.chatter, version=4.4, platformVersion=4.1, databaseEnabled=false, deviceName=Android, platformName=Android, webStorageEnabled=false, warnings={}, takesScreenshot=true}]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:102)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:352)
at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:449)
at org.openqa.selenium.By$ByXPath.findElement(By.java:357)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:344)
at com.a.b.c.NewTest.f(NewTest.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)


And I am experiencing one more thing very peculiar. I tried giving 6 seconds wait time and it was able to write user name. The next time when I ran giving same wait period it failed with same error log. The next time when I gave a little more wait time(7 seconds) it worked well. So Every time I had to give wait period more than previous time. This way I tried with 6 sec, 7 sec, 3 sec, 9 sec, 12 sec, 15 sec.
And the result was pass, pass, fail, pass, pass, pass.

I am finding it difficult to understand this particular behavior.
I am using the following env.
Android - 4.4
MAC-10.9.5
Xcode - 6
IOS-8
Selenium-server-standalone-2.44
Appium Java-client-1.7.0

Kindly help in figuring out the above problem.

Thanks
Suryakanta

try with the code:
int tap=0;
while(++tap<=7){

try{
driver.findElement(By.xpath()).sendkeys();
break;}
catch(WebDriverException e){
Thread.sleep(1000);
continue;
}
let me know if you have still issue .