Capabilities issue running through grid

[cdnyoung]

The problem

When kicking off our test runs (via Bamboo) on a Selenium Grid, the device log returns an error that appears to be related to how the capabilities are being read. I've been trying to find examples of formatting for capabilities, but haven't really found anything definitive.

1. Can anyone take a look at the log below and let me know where the issue might be?
2. How are the 'first match' and 'always match' caps supposed to be formatted, and for that matter, how are all the caps supposed to be formatted?

Environment

• Appium version (or git revision) that exhibits the issue: 1.10
• Last Appium version that did not exhibit the issue (if applicable): 1.8.2-beta
• Desktop OS/version used to run Appium: N/A
• Mobile platform/version under test: iOS 12.1
• Real device or emulator/simulator: Real Device (iPad)

Details

Not sure as an older version of Appium (1.8.2-beta) works with my configuration..

Link to Appium logs

https://gist.github.com/cdnyoung/243625ce1a75a31091d1f78670a716d3

[mykola-mokhnach]

Make sure the java client version is up to date and does not have selenium API version overridden in your project config.

[cdnyoung]

I'm using:
group: 'io.appium', name: 'java-client', version: '6.1.0'
and
group: 'org.seleniumhq.selenium', name: 'selenium-java', version: '3.13.0' as is indicated in the logs..

would I need to add additional dependencies such as:
https://mvnrepository.com/artifact/org.seleniumhq.selenium/selenium-api/3.13.0

It looks like those would be included with the dependency:
org.seleniumhq.selenium', name: 'selenium-java', version: '3.13.0

Older versions of appium haven't required this AKAIK..

[mykola-mokhnach]

Like I said you must NOT override selenium API version. Let java client to retrieve the one, which is set in its config

[cdnyoung]

OK sorry, I don't know what you mean by that. Do you mean let the Appium java client retrieve the selenium API version? Should I just remove the Selenium dependencies entirely? This wasn't the case with older versions of Appium, AKAIK..

[cdnyoung]

I removed the dependency, and the version showing in the logs now is 3.12.0 (for selenium). Unfortunately the issue remains. Same errors as in original gist.

[mykola-mokhnach]

java client 6.1.0 is bundled with API v 3.14. Also the hub itself should be up to date

[cdnyoung]

Thank you, I've updated the api to 3.14 as well, still the same error. Please see the following. Any idea what could be causing this?

Hub's also at 3.14.
Do you think there is anything to the way the log is formatting the capabilities? Maybe I do have them formatted incorrectly?

https://gist.github.com/cdnyoung/71bcc9043d112b66b66805b11e2768b9

[mykola-mokhnach]

Install the most recent java client from jitpack like it is described in https://github.com/appium/java-client. The Maven snapshot does not seem to contain the necessary fixes

[mykola-mokhnach]

@BrunoCarvalho18 Do you mind to help this gentlemen with the same problem?
I move the original issue into java client issues tracker, since it has nothing to do with the server.

[BrunoCarvalho18]

Mykola-Mokhnach,

I can help the gentlemen yes.

Thank You.

Best Regards,
Bruno Carvalho.

[BrunoCarvalho18]

@cdnyoung, I'm using this dependencies in my pom.xml: https://gist.github.com/BrunoCarvalho18/12c9a2d88fc6b4d550f1d117f3efe2db, it's working now.

Best Regards,
Bruno Carvalho.

[cdnyoung]

Thanks, @BrunoCarvalho18 . Unfortauntely, it's not working with that configuration. I can't get my project to compile using appium client 6.0.0 and, really any, version of selenium.
Any other suggestions for this?

[BrunoCarvalho18]

@cdnyoung , show your console and logcat, please ?

[cdnyoung]

Hi @BrunoCarvalho18 here's a link to the latest device log using the latest appium java-client commit.

https://gist.github.com/cdnyoung/cf1c6bdbcfc5226b714b220c5cd5c09b

and the Appium log (which doesn't tell too much)...

https://gist.github.com/cdnyoung/8b66d47c6de87561a0cde160d7e4e947

Thanks for your help. We're going into the holiday break, so I may not be able to be as responsive but if you have any idea as to a proper configuration, I'd appreciate it. Like I mentioned before, I wasn't able to get the 6.0.0 version going, and I can't tell which of the capabilities it is getting stuck on, but I've triple-checked the device and it's configuration to make sure it's matching the capabilities listed.

Do you think this is a compatibility issue with the appium server version, java-client version, etc? From what I understand, there is some combination that should work, but I must be missing something.
Thanks!