InvalidSelectorError: Locator Strategy 'css selector' is not supported for this session

[Madhavip3]

Description

Updated Appium to the latest version and started seeing this issue. Tried using AppiumDriver and iOS Driver and still see the issue. Running Appium on native apps on both iOS and UWP. Currently we get this issue on iOS. Worked perfectly fine until the previous release.

Environment

Java Client version: 6.1.0
Appium Server :Version 1.7.1 (1.7.1.20180926.9)
OS Version:10.13.6 (17G2112)
Mobile Platform version: IOS 11.4(iPads)
Device:Simulator

##Code used
currentSession.findElement(By.id(id)).click() --> this is how we are accessing the elements in the app. Also Tried findElementById() with IOSDriver and still see the same issue.

[saikrishna321]

Can you please post logs and update your appium server to latest

[Madhavip3]

I updated to the latest version and now the version is
Version 1.8.0 (1.8.0.20181023.4)

[Madhavip3]

appium-server-logs.txt

[saikrishna321]

@Madhavip3 you cant use css selector for Native app its only applied on web context

[Madhavip3]

@saikrishna321 I am not using Css selector. That was the bug I raised.I have nowhere css selector mentioned in the code.
As mentioned before the code used is currentSession.findElement(By.id(id)).click() - I am using find elementByid .
I am also testing this version with running only this line of code.

[Madhavip3]

Just to re-iterate, everything is working fine with Appium desktop version Version 1.6.3 (1.6.3). This is where I originally posted the issue
appium/appium#10874 (comment).
There are also other people reporting this issue.

[saikrishna321]

@Madhavip3 issue posted in #10874 was python client issue on selenium side.

I'm not able to reproduce the issue on latest java-client with latest appium beta.

[debug] [W3C (6f5b4adc)] Calling AppiumDriver.findElement() with args: ["id","org.wordpress.android:id/nux_username","6f5b4adc-c587-4c04-a26c-c91e46817060"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -android uiautomator
[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [JSONWP Proxy] Matched '/element' to command name 'findElement'
[debug] [JSONWP Proxy] Proxying [POST /element] to [POST http://localhost:8200/wd/hub/session/83777206-3b39-4f8f-a12d-cff5b3f04d6e/element] with body: {"strategy":"id","selector":"org.wordpress.android:id/nux_username","context":"","multiple":false}

[Madhavip3]

@saikrishna321 What is the latest java client version you are using?

[Madhavip3]

I am trying this on iOS. I see that you have tried it on android. Can you try it on iOS as well?Thanks!

[saikrishna321]

[debug] [W3C (b6b18050)] Responding to client with driver.findElement() result: {"element-6066-11e4-a52e-4f735466cecf":"1D000000-0000-0000-1D64-010000000000"}
[HTTP] <-- POST /wd/hub/session/b6b18050-94e2-424b-9220-a06fb78e8280/element 200 89 ms - 88
[HTTP]
[HTTP] --> POST /wd/hub/session/b6b18050-94e2-424b-9220-a06fb78e8280/element
[HTTP] {"using":"id","value":"nextButton"}
[debug] [W3C (b6b18050)] Calling AppiumDriver.findElement() with args: ["id","nextButton","b6b18050-94e2-424b-9220-a06fb78e8280"]
[debug] [XCUITest] Executing command 'findElement'
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, name, class name, -ios predicate string, -ios class chain, accessibility id
[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [JSONWP Proxy] Matched '/element' to command name 'findElement'
[debug] [JSONWP Proxy] Proxying [POST /element] to [POST http://localhost:8100/session/786553E8-29B7-417A-A43E-751D994C9D5B/element] with body: {"using":"id","value":"nextButton"}

I use the latest master commit

https://github.com/appium/java-client#maven

[Madhavip3]

@saikrishna321 I tried with the latest commit and I still see the same issue. Is there anything else I am missing here?
appium-server-logs.txt

[helenren]

Hit the same issue once using appium from 1.8.1 to 1.9.0 trying to use by.name to find an element on a native context using ios 11.4 simulator.

For 1.8,1, for creating a new session, got this back:
org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS
While for 1.9.0, got this back:
Oct 30, 2018 9:03:32 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: W3C.
Feel since the new session using W3C, so use W3CHttpCommandCodec for the command encode, which make the command like this:
2018-10-31 04:03:32:328 - �[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session/de917d18-aa03-43da-915a-994f025a9506/elements�[39m
2018-10-31 04:03:32:328 - �[35m[HTTP]�[39m �[90m{"value":"*[name='EULA.agree']","using":"css selector"} and hit this error: Encountered internal error running command: InvalidSelectorError: Locator Strategy 'css selector' is not supported for this session.