René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bugs in errorcodes parsing with lateset selenium3 beta 4","articleBody":"## Description\n\nNO_SUCH_ELEMENT can't be parsed.\nNPE. Please see the attachment at the end for stacktrace.\n## Environment\n\njava8\nAppium1.5.2\nMAC\nAndroid\n## Details\n\nWith the latest selenium(selenium3 beta 4) and appium1.5.2:\nWhen \"NO_SUCH_ELEMENT\" error is parsed,\n 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.\n## Code To Reproduce Issue [ Good To Have ]\n\ncall findElement when the element is not displayed\n## Ecxeption stacktraces\n\nplease see attachment.\n\u003cimg width=\"1122\" alt=\"screen shot 2016-10-03 at 10 43 01 am\" src=\"https://cloud.githubusercontent.com/assets/3776782/19295909/8cb16db8-8fec-11e6-8344-14a904322281.png\"\u003e\n","author":{"url":"https://github.com/wangxf1030","@type":"Person","name":"wangxf1030"},"datePublished":"2016-10-12T02:54:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/488/java-client/issues/488"}