Test Script not able to locate element on Real Device post switching to webview of a hybrid app. about appium-chromedriver HOT 9 OPEN

Those don't look like Appium logs

from appium-chromedriver.

Your client code also appears to be using some kind of framework so it's not really possible to understand what commands are being run without seeing the Appium logs

from appium-chromedriver.

Hi Jlipps,
I have attached the appium logs for your reference in the issue description. Sharing again

Link to Appium logs
1..Appium logs for working code on emulator on successful switch context to webview and able to locate element.

2. Appium logs on real device on successful switch context to webview but not able to locate element.

Links to chromedriver Logs
Chromedriver getpagesource() response logs on emulator.

Chromedriver getpagesource() response logs on real device.

Please Suggest.

from appium-chromedriver.

It seems like the chromedriver/chrome browser version itself could not find it.

�[35m[WD Proxy]�[39m Got response with status 404: {"value":{"error":"no such element","message":"no such element: Unable to locate element: {"method":"xpath","selector":"//input[@data-autoid='LASTNAME_ctrl']"}\n (Session info: chrome=98.0.4758.101)","stacktrace":"Backtrace:\n\tOrdinal0 [0x0076A0A3+2597027]\n\tOrdinal0 [0x006FBA61+2144865]\n\tOrdinal0 [0x005F3C58+1064024]\n\tOrdinal0 [0x0062020E+1245710]\n\tOrdinal0 [0x0062040B+1246219]\n\tOrdinal0 [0x0064A722+1419042]\n\tOrdinal0 [0x006387F4+1345524]\n\tOrdinal0 [0x00648B1A+1411866]\n\tOrdinal0 [0x006385C6+1344966]\n\tOrdinal0 [0x006154C6+1201350]\n\tOrdinal0 [0x006163B6+1205174]\n\tGetHandleVerifier [0x009110A2+1681842]\n\tGetHandleVerifier [0x009C3B0C+2413596]\n\tGetHandleVerifier [0x00801221+568113]\n\tGetHandleVerifier [0x007FFFA3+563379]\n\tOrdinal0 [0x0070174E+2168654]\n\tOrdinal0 [0x00706538+2188600]\n\tOrdinal0 [0x00706680+2188928]\n\tOrdinal0 [0x0071030C+2229004]\n\tBaseThreadInitThunk [0x74FDFA29+25]\n\tRtlGetAppContainerNamedObjectPath [0x77007A9E+286]\n\tRtlGetAppContainerNamedObjectP...

Chromedriver on Real Device used: 98.0.4758.48
Chromedriver on Emulator used: 83.0.4103.106

One possible reason from this comment is newer chrome/chromedriver cannot find them. If you have a device that has older chrome, you can try it out...

from appium-chromedriver.

Hi KazuCocoa,
I have used chromedriver 83.0.4103.106 on emulator it is working fine. When i am using chromedriver 98.0.4758.48 or chromedriver 99.0.4844.73 on real device i am getting unable to locate element error.

from appium-chromedriver.

Yes, so I assume older chrome version and chromedriver for Android might work.
Kindly report it to Google.

from appium-chromedriver.

You also can create a Play Store available emulator instance and update the chrome to v98 to confirm if it is chrome/chromedriver dependent or manufacture dependent.

from appium-chromedriver.

Hi KazuCocoa,
I am able to run my script on chromedriver 83.0.4103.106 on emulator and on chromedriver 81.0.4044.138 on real device. However when i am running it on chromedriver 99.0.4844.73 with browser version 99.0.4844.73 on real device i am getting message "Unable to locate element.". Moreover i have also tried to downgrade my chromebrowser version to 98.0.4758.101 and used chromedriver 98.0.4758.102 also tried the similar activity for
chromebrowser version to 97.0.4692.70 and used chromedriver 97.0.4692.71. But for downgraded version apk i am getting the message No chromederiver found for chrome browser version 99.0.4844.73.

(Steps used for downgrading chromebrowser version 1. Disable autoupdate 2. Uninstall updates for chromedriver 3. Install the downgrade version browser apk. 4 Install the chromedriver version matching the browser apk .)

from appium-chromedriver.

Perhaps the android WebView's chrome browser version was v99.

No chromederiver found for chrome browser version 99.0.4844.73.

Generally it means the app's webview process runs as chrome browser v99, and the chromedriver cannot work with it because of lower chromedriver version than the chrome version.

I am able to run my script on chromedriver 83.0.4103.106 on emulator and on chromedriver 81.0.4044.138 on real device.

Hm, it sounds like chrome/chromedriver has kind of regressions. Then, only Google can improve it...

from appium-chromedriver.