This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Dec 2018
23 / 40
Dec 2018
Jan 2019
KazuCocoa
Dec '18
vsharma

I tried to run https://github.com/appium/java-client/blob/1991a8a0f9e4a3ff467dbb713cb5c51c8edc060f/src/test/java/io/appium/java_client/ios/IOSDriverTest.java1 with 3.13.0, 3.14 and 3.141.59. 3.13 and 3.14 succeeded to run. 3.141.59 had an issue in probably grid side? (have not investigated though). The grid configuration was he same as ruby_core’s one I attached the above.

[HTTP] --> GET /wd/hub/status
[HTTP] {}
[debug] [GENERIC] Calling AppiumDriver.getStatus() with args: []
[debug] [GENERIC] Responding to client with driver.getStatus() result: {"build":{"version":"1.11.0-beta.2","git-sha":"e793e279f91217301e809e5deaad0b85ce0c3802","built":"2018-12-21 17:20:20 -0500"}}
[HTTP] <-- GET /wd/hub/status 200 1 ms - 164
[HTTP]
[HTTP] --> POST /wd/hub/session
[HTTP] {"desiredCapabilities":{"app":"/Users/kazu/GitHub/java-client/src/test/java/io/appium/java_client/TestApp.app.zip","server:CONFIG_UUID":"41d25297-cc13-49cc-ad8a-8b78ac18f327","platformVersion":"11.4","automationName":"XCuiTest","platformName":"ios","deviceName":"iPhone X","launchTimeout":500000},"capabilities":{"firstMatch":[{"platformName":"ios","server:CONFIG_UUID":"41d25297-cc13-49cc-ad8a-8b78ac18f327"}]}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"app":"/Users/kazu/GitHub/java-client/src/test/java/io/appium/java_client/TestApp.app.zip","server:CONFIG_UUID":"41d25297-cc13-49cc-ad8a-8b78ac18f327","platformVersion":"11.4","automationName":"XCuiTest","platformName":"ios","deviceName":"iPhone X","launchTimeout":500000},null,{"firstMatch":[{"platformName":"ios","server:CONFIG_UUID":"41d25297-cc13-49cc-ad8a-8b78ac18f327"}]}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at 1545836171483 (23:56:11 GMT+0900 (Japan Standard Time))
[Appium] Could not parse W3C capabilities: 'deviceName' can't be blank
[Appium] Trying to fix W3C capabilities by merging them with JSONWP caps
[BaseDriver] The capabilities ["app","platformVersion","automationName","deviceName","launchTimeout"] are not standard capabilities and should have an extension prefix
[Appium] Creating new XCUITestDriver (v2.104.0) session
[Appium] Capabilities:
[Appium]   app: /Users/kazuaki/GitHub/java-client/src/test/java/io/appium/java_client/TestApp.app.zip
[Appium]   platformVersion: 11.4
[Appium]   automationName: XCuiTest
[Appium]   deviceName: iPhone X
[Appium]   launchTimeout: 500000
[Appium]   platformName: ios
[Appium]   server:CONFIG_UUID: 41d25297-cc13-49cc-ad8a-8b78ac18f327
[debug] [BaseDriver] W3C capabilities {"alwaysMatch":{"appium:app... and MJSONWP desired capabilities {"app":"/Users/kazuaki/GitH... were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {"alwaysMatch":{"appium:app...
[BaseDriver] The following capabilities were provided, but are not recognized by appium: server:CONFIG_UUID.
[BaseDriver] Session created with session id: d1173cec-ecea-432b-b530-3ec659d56d08
[debug] [XCUITest] Current user: 'kazuaki'
[HTTP] --> GET /wd/hub/status
[HTTP] {}
[debug] [GENERIC] Calling AppiumDriver.getStatus() with args: []

The above was a part of Appium log which was registered with the grid. Appium clients worked well.

I noticed capabilities you attached in https://discuss-new.appium.io/uploads/default/original/2X/f/fe7545f06f408ed5e9cd3486ec08f76820745d84.JPG3 was grid side. What capability can you see in http://localhost:4444/grid/console ? Was it correct?

vsharma
Dec '18
1

@KazuCocoa today I tried again this time I added device name in parameter and did a rerun…
I see some other exception in logs
the value “appium:udid”: “ZY2235F2FB”, is displayed as expected in logs though… but there is exception

2018-12-27 16:39:53.673:WARN:osjs.HttpChannel:qtp510464020-12: /wd/hub/session java.io.IOException: org.openqa.grid.common.exception.GridException: Cannot extract a capabilities from the request: {
“desiredCapabilities”: {
“app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd.apk”,
“appActivity”: “abc”,
“appPackage”: “abc”,
“autoGrantPermissions”: “true”,
“platformName”: “Android”,
“udid”: “ZY2235F2FB”,
“deviceName”: “Motorola”,
“fullReset”: “false”,
“version”: “6.0.1”,
“platform”: “ANDROID”,
“systemPort”: “5001”
},
“capabilities”: {
“firstMatch”: [
{
“appium:app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd.apk”,
“appium:appActivity”: “”,
“appium:appPackage”: “”,
“appium:autoGrantPermissions”: “true”,
“appium:deviceName”: “Motorola”,
“appium:fullReset”: “false”,
“platform”: “ANDROID”,
“platformName”: “android”,
“appium:systemPort”: “5001”,
“appium:udid”: “ZY2235F2FB”,
“version”: “6.0.1”
}
]
}

org.openqa.selenium.WebDriverException: java.lang.NullPointerException
Build info: version: ‘3.141.5’, revision: ‘d54ebd709a’, time: '2018-11-06T11:42:16’
System info: host: ‘VAIBHAVS-LAPTOP’, ip: ‘192.168.56.1’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: '1.8.0_51’
Driver info: driver.version: unknown
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:192)
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:1)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:249)
at io.appium.java_client.pagefactory.AppiumElementLocator.waitFor(AppiumElementLocator.java:99)
at io.appium.java_client.pagefactory.AppiumElementLocator.findElement(AppiumElementLocator.java:119)
at io.appium.java_client.pagefactory.interceptors.InterceptorOfASingleElement.intercept(InterceptorOfASingleElement.java:59)
at org.openqa.selenium.remote.RemoteWebElement$$EnhancerByCGLIB$$d27c0df4.getText()
at TestCases.Smoke.StartEkyc(Smoke.java:31)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at io.appium.java_client.pagefactory.AppiumElementLocator.lambda$0(AppiumElementLocator.java:120)
at io.appium.java_client.pagefactory.AppiumElementLocator$$Lambda$214/1013481204.get(Unknown Source)
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:172)
… 20 more
Devicename

cyoung2727
Dec '18

I’m having the same issue on an iOS device and am very interested to hear a solution for this.

KazuCocoa
Dec '18

The 1st issue you could not establish a new connection was resolved, right? Your attached capabilities had no issue like you faced before. And you could send a command find_element to the target.

at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:192)
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:1)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:249)
at io.appium.java_client.pagefactory.AppiumElementLocator.waitFor(AppiumElementLocator.java:99)
at io.appium.java_client.pagefactory.AppiumElementLocator.findElement(AppiumElementLocator.java:119)

I would like to know that request send to server. Could you attach full server log via Gist or something? (I think you cannot attach all of them in here.)

vsharma
Dec '18

[quote=“KazuCocoa, post:22, topic:24669”]
I would like to know that request send to server. Could you attach full server log via Gist or something?
@KazuCocoa I am going through blogs to understand capture of server logs…
In eclipse workspace I do see logs in console logs and same can be found in workspace.
Found belwo link need to implement capture of server logs or is there any other way? where I can get the logs present? for your sharing


As far the changes made in request in

  1. In testng.xml I had added the deviceName parameter same I passed into @Parameters
  2. Yesterday I was reading to invoke web on device for that i made change in chromedriver which I think has nothing to do but was getting some error in logs had added org.slf4j

Apart from that I made no changes…

KazuCocoa
Dec '18

Sorry, I’m not sure running via Eclipse case…

In my case:
terminal1: Launch a grid server
terminal2: Launch an appium server (and communicate with the grid)
terminal3 or other place: Run Java test case

Then, outputs in terminal 1, 2 and 3 will be logs for each products.
If you can also follow this way, it’s the easiest way, I think

KazuCocoa
Dec '18

that is just a bach environment. (On macOS, “terminal” is build-in app name.)

cyoung2727
Dec '18

Hi @vsharma, you bet. I’ll get that set up and see what I can get. It’s going to be after next week though, as I’ll be unavailable over next week. So, don’t lose patience. I’ll be back!

I’ve been working on this problem for a few months now, and unfortunately, haven’t been able to fix it, even with running those latest commits from the java-client project. It started after having to upgrade our devices, so I believed there to be some compatibility issue between dependencies (as has been stated before).

But, I also started looking at this locally, and when I tried to start a hub and a node, I get an error around the hub config not being able to be read… as if it’s not parsing the config json correctly… that’s the next avenue I’m going to explore. In the meantime…

One config that worked for me was to downgrade appium server to 1.8.2-beta (with java bindings at 4.1.2, and selenium versions 3.0.1). This config doens’t really allow more than one device to run successfully, but it’s something and not nothing (as is the case with these newer versions).

vsharma
Jan '19

Hi @KazuCocoa logs are as below
I am still not able to get the case when the data was displayed in way as value:parameter as initial case… not sure what had caused the same.
selenium-server-standalone-3.141.59.jar
Client 6.1.0

Please let me know what combination I should try to run… (I have changed the name of apk to abcd and other data)

18:19:00.792 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
18:19:00.995 INFO [GridLauncherV3.lambda$buildLaunchers$5] - Launching Selenium Grid hub on port 4444
2019-01-01 18:19:01.448:INFO::main: Logging initialized @1124ms to org.seleniumhq.jetty9.util.log.StdErrLog
18:19:01.994 INFO [Hub.start] - Selenium Grid hub is up and running
18:19:01.994 INFO [Hub.start] - Nodes should register to http://192.168.1.102:4444/grid/register/
18:19:01.994 INFO [Hub.start] - Clients should connect to http://192.168.1.102:4444/wd/hub
18:20:45.136 INFO [DefaultGridRegistry.add] - Registered a node http://127.0.0.1:5000
18:20:59.582 INFO [DefaultGridRegistry.add] - Registered a node http://127.0.0.1:5001
2019-01-01 18:21:50.059:WARN:osjs.HttpChannel:qtp510464020-16: /wd/hub/session java.io.IOException: org.openqa.grid.common.exception.GridException: Cannot extract a capabilities from the request: {
“desiredCapabilities”: {
“app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd.apk”,
“appActivity”: “abcd”,
“appPackage”: “abcd”,
“autoGrantPermissions”: “true”,
“platformName”: “Android”,
“udid”: “ZY2235F2FB”,
“deviceName”: “Motorola”,
“fullReset”: “false”,
“version”: “6.0.1”,
“platform”: “ANDROID”,
“systemPort”: “5001”
},
“capabilities”: {
“firstMatch”: [
{
“appium:app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd.apk”,
“appium:appActivity”: “abcd”,
“appium:appPackage”: “abcd”,
“appium:autoGrantPermissions”: “true”,
“appium:deviceName”: “Motorola”,
“appium:fullReset”: “false”,
“platform”: “ANDROID”,
“platformName”: “android”,
“appium:systemPort”: “5001”,
“appium:udid”: “ZY2235F2FB”,
“version”: “6.0.1”
}
]
}
}
2019-01-01 18:21:50.059:WARN:osjs.HttpChannel:qtp510464020-19: /wd/hub/session java.io.IOException: org.openqa.grid.common.exception.GridException: Cannot extract a capabilities from the request: {
“desiredCapabilities”: {
“app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd.apk”,
“appActivity”: “abcd”,
“appPackage”: “abcd”,
“autoGrantPermissions”: “true”,
“platformName”: “Android”,
“udid”: “7e6faae4”,
“deviceName”: “Lenevo”,
“fullReset”: “false”,
“version”: “5.1.1”,
“platform”: “ANDROID”,
“systemPort”: “5000”
},
“capabilities”: {
“firstMatch”: [
{
“appium:app”: “C:\Users\vaibhav.sharma\Latest WorkSpace\IDIAutomation\src\main\abcd”,
“appium:appActivity”: “abcd”,
“appium:appPackage”: “abcd”,
“appium:autoGrantPermissions”: “true”,
“appium:deviceName”: “Lenevo”,
“appium:fullReset”: “false”,
“platform”: “ANDROID”,
“platformName”: “android”,
“appium:systemPort”: “5000”,
“appium:udid”: “7e6faae4”,
“version”: “5.1.1”
}
]
}
}

KazuCocoa
Jan '19

Could you try with 3.14?
I faced an issue with 3.141.59 before as I addressed in previous comment. (I haven’t taken a look yet.)

And can you share your appium server log?
Your attached log was grid’s log. If something happens between Grid and Appium server, we probably can observe something there.

vsharma
Jan '19

@KazuCocoa I did change all dependency to 3.14 … below are the logs console
3.13 I tried but getting errors for jar compatibility

org.openqa.selenium.WebDriverException: java.lang.NullPointerException
Build info: version: ‘3.14.0’, revision: ‘aacccce0’, time: '2018-08-02T20:19:58.91Z’
System info: host: ‘VAIBHAVS-LAPTOP’, ip: ‘192.168.56.1’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: '1.8.0_51’
Driver info: driver.version: unknown
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:192)
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:1)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:260)
at io.appium.java_client.pagefactory.AppiumElementLocator.waitFor(AppiumElementLocator.java:99)
at io.appium.java_client.pagefactory.AppiumElementLocator.findElement(AppiumElementLocator.java:119)
at io.appium.java_client.pagefactory.interceptors.InterceptorOfASingleElement.intercept(InterceptorOfASingleElement.java:59)
at org.openqa.selenium.remote.RemoteWebElement$$EnhancerByCGLIB$$d27c0df4.getText()
at TestCases.Smoke.StartEkyc(Smoke.java:31)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at io.appium.java_client.pagefactory.AppiumElementLocator.lambda$0(AppiumElementLocator.java:120)
at io.appium.java_client.pagefactory.AppiumElementLocator$$Lambda$283/336833475.get(Unknown Source)
at io.appium.java_client.pagefactory.AppiumElementLocator$WaitingFunction.apply(AppiumElementLocator.java:172)
… 20 more

KazuCocoa
Jan '19

Can you share a log like below which is available by Appium server?

$ appium
[Appium] Welcome to Appium v1.11.0-beta.2 (REV e793e279f91217301e809e5deaad0b85ce0c3802)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session
[HTTP] {"desiredCapabilities":{"platformName":"ios","automationName":"XCUITest","app":"/Users/kazuaki/GitHub/ruby_lib_core/test/functional/app/UICatalog.app.zip","platformVersion":"11.4","deviceName":"iPhone 8","useJSONSource":true,"someCapability":"some_capability","newCommandTimeout":120,"wdaLocalPort":8100,"waitForQuiescence":true,"reduceMotion":true,"screenshotQuality":2},"capabilities":{"firstMatch":[{"platformName":"ios","appium:automationName":"XCUITest","appium:app":"/Users/kazuaki/GitHub/ruby_lib_core/test/functional/app/UICatalog.app.zip","appium:platformVersion":"11.4","appium:deviceName":"iPhone 8","appium:useJSONSource":true,"appium:someCapability":"some_capability","appium:newCommandTimeout":120,"appium:wdaLocalPort":8100,"appium:waitForQuiescence":true,"appium:reduceMotion":true,"appium:screenshotQuality":2}]}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"platformName":"ios","automationName":"XCUITest","app":"/Users/kazuaki/GitHub/ruby_lib_core/test/functional/app/UICatalog.app.zip","platformVersion":"11.4","deviceName":"iPhone 8","useJSONSource":true,"someCapability":"some_capability","newCommandTimeout":120,"wdaLocalPort":8100,"waitForQuiescence":true,"reduceMotion":true,"screenshotQuality":2},null,{"firstMatch":[{"platformName":"ios","appium:automationName":"XCUITest","appium:app":"/Users/kazuaki/GitHub/ruby_lib_core/test/functional/app/UICatalog.app.zip","appium:platformVersion":"11.4","appium:deviceName":"iPhone 8","appium:useJSONSource":true,"appium:someCapability":"some_capability","appium:newCommandTimeout":120,"appium:wdaLocalPort":8100,"appium:waitForQuiescence":true,"appium:reduceMotion":true,"appium:screenshotQuality":2}]}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at 1546597779810 (19:29:39 GMT+0900 (Japan Standard Time))
[Appium] Creating new XCUITestDriver (v2.104.0) session
[Appium] Capabilities:
[Appium]   platformName: ios
[Appium]   automationName: XCUITest
[Appium]   app: /Users/kazuaki/GitHub/ruby_lib_core/test/functional/app/UICatalog.app.zip
[Appium]   platformVersion: 11.4
[Appium]   deviceName: iPhone 8
[Appium]   useJSONSource: true
[Appium]   someCapability: some_capability
[Appium]   newCommandTimeout: 120
[Appium]   wdaLocalPort: 8100
[Appium]   waitForQuiescence: true
[Appium]   reduceMotion: true
[Appium]   screenshotQuality: 2
[debug] [BaseDriver] W3C capabilities {"alwaysMatch":{"platformNa... and MJSONWP desired capabilities {"platformName":"ios","auto... were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {"alwaysMatch":{"platformNa...
[BaseDriver] The following capabilities were provided, but are not recognized by appium: someCapability.
[BaseDriver] Session created with session id: 9eee4bb2-8afa-431e-b772-d0080855648e
(node:49664) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
...
vsharma
Jan '19

@Aleksei I am confused can you advise as what are server logs as requested above.In eclipse console I see logs which log is that…
As I am using eclipse in workspace I do see a log folder.

@KazuCocoa
As read on forums I have implemented the code and the below line throws exception…Till I get some some from Aleksei may be it can be some hint
Log.info(" Thread below* ");
ThreadLocalDriver.setTLDriver(new AndroidDriver(new URL(“http://127.0.0.1:4444/wd/hub”),capabilities));
driver = ThreadLocalDriver.getTLDriver();

vsharma
Jan '19

@Aleksei my … I should have been more clear I needed info on Selenium log what Kazu is asking for.