bugs in errorcodes parsing with lateset selenium3 beta 4

[wangxf1030]

Description

NO_SUCH_ELEMENT can't be parsed.
NPE. Please see the attachment at the end for stacktrace.

Environment

java8
Appium1.5.2
MAC
Android

Details

With the latest selenium(selenium3 beta 4) and appium1.5.2:
When "NO_SUCH_ELEMENT" error is parsed,
ErrorCodesMobile.getExceptionType(int) is supposed to call ErrorCodes.getExceptionType(int) , and within that method it should call ErrorCodes.getExceptionType(string). However, ErrorCodes.getExceptionType(string) is overrided by ErrorCodesMobile, but it doesn't call ErrorCodes.getExceptionType(string), instead it thorws NPE.

Code To Reproduce Issue [ Good To Have ]

call findElement when the element is not displayed

Ecxeption stacktraces

please see attachment.

[TikhomirovSergey]

The migration to Selenium 3 is planned. But we have not started it yet.

[SrinivasanTarget]

I'm not able to reproduce this.Can you paste the entire logs inform of gist. It throws NSE exception perfectly for me in Selenium 3.0 with Java-Client #489

[SrinivasanTarget]

Also let us know what you are exactly trying to do.