I have two table in one view. In right side table i am able to perform action but unable to tap on left side table.
when i have tried by appium inspector, here is it invisible but i am able to tap on is by my application.
An unknown server-side error occurred while processing the command. (WARNING: The server did not provide any stacktrace information)
ts()[13].elements()[1].tap()
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: target.frontMostApp().elements()[0].elements()[13].elements()[1].scrollToVisible()
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: target.frontMostApp().elements()[0].elements()[13].elements()[1] - scrollToVisible cannot be used because this element has no scrollable ancestor.
info: [IOS_SYSLOG_ROW ] Jun 5 13:04:07 anuj MobileGestaltHelper[76] : libMobileGestalt MobileGestalt.c:273: server_access_check denied access to question UniqueDeviceID for pid 1183
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: target.frontMostApp().elements()[0].elements()[13].elements()[1] - scrollToVisible cannot be used because this element has no scrollable ancestor.
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: target.frontMostApp().elements()[0].elements()[13].elements()[1] could not be tapped because the element is not visible
info: [IOS_SYSLOG_ROW ] Jun 5 13:04:07 anuj ScriptAgent[1183] : libMobileGestalt MobileGestaltSupport.m:170: pid 1183 (ScriptAgent) does not have sandbox access for re6Zb+zwFKJNlkQTUeT+/w and IS NOT appropriately entitled
info: [IOS_SYSLOG_ROW ] Jun 5 13:04:07 anuj ScriptAgent[1183] : libMobileGestalt MobileGestalt.c:534: no access to UniqueDeviceID (see rdar://problem/11744455)
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Error: VerboseError: elementId 5 could not be tapped
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Error: Error during eval: tapById@file:///Applications/Appium.app/Contents/Resources/node_modules/appium/EFBCEA0A-8BCB-4B94-9CD0-EF8DA95CBF83/bootstrap-d5a0fb924946d8d3.js:1110:25
eval code
eval@[native code]
startProcessing@file:///Applications/Appium.app/Contents/Resources/node_modules/appium/EFBCEA0A-8BCB-4B94-9CD0-EF8DA95CBF83/bootstrap-d5a0fb924946d8d3.js:2693:30
bootstrap@file:///Applications/Appium.app/Contents/Resources/node_modules/appium/EFBCEA0A-8BCB-4B94-9CD0-EF8DA95CBF83/bootstrap-d5a0fb924946d8d3.js:2761:31
global code@file:///Applications/Appium.app/Contents/Resources/node_modules/appium/EFBCEA0A-8BCB-4B94-9CD0-EF8DA95CBF83/bootstrap-d5a0fb924946d8d3.js:2770:10
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: responding with:
info: [debug] [INST] 2015-06-05 07:34:07 +0000 Debug: Running system command #16: /Applications/Appium.app/Contents/Resources/node/bin/node /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-uiauto/bin/command-proxy-client.js /tmp/instruments_sock 2,{“status”:13,“value”:“elementId 5 could not be tapped”}…
info: [debug] Socket data received (57 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {“status”:13,“value”:“elementId 5 could not be tapped”}
info: [debug] Responding to client with error: {“status”:13,“value”:{“message”:“An unknown server-side error occurred while processing the command.”,“origValue”:“elementId 5 could not be tapped”},“sessionId”:“0a2db9b2-81bc-44f1-859f-8fe3b9eeb867”}
info: <-- POST /wd/hub/session/0a2db9b2-81bc-44f1-859f-8fe3b9eeb867/element/5/click 500 1274.238 ms - 200
info: --> DELETE /wd/hub/session/0a2db9b2-81bc-44f1-859f-8fe3b9eeb867 {}