Tableview cell access issue on appium 1.5.3 and real iOS device

Hi,
Im’ using Appium 1.5.3, Mac Sierra and iPhone 4s with iOS 9.3.5 and python.
I can run the test in Instrument, can access every element.
When I run the python version on appium i have problem accessing elements. Mainly the tableview cells.
It comes back with the
libMobileGestalt MobileGestalt.c:281: server_access_check denied access error.
Any help would be apritiated.
I tried different methods to access the element:
command = ‘.tableViews()[0].cells()[“Switch Camera”]’
wd.find_element_by_ios_uiautomation(command).click()
wd.find_element_by_xpath("//UIAApplication[1]/UIAWindow[1]/UIATableCell[2]").click()
wd.find_element_by_id(“Switch Camera”).click()
None of them worked.
here is the appium log detail:

[debug] [Instruments] [INST] 2017-02-03 15:55:33 +0000 Debug: Got new command 22 from instruments: au.getElementByAccessibilityId(‘Cedar 10 iPhone 4 iOS7’)

[debug] [Instruments] [INST] 2017-02-03 15:55:33 +0000 Debug: evaluating au.getElementByAccessibilityId(‘Cedar 10 iPhone 4 iOS7’)

[debug] [Instruments] [INST] 2017-02-03 15:55:33 +0000 Debug: evaluation finished
[debug] [Instruments] [INST] 2017-02-03 15:55:33 +0000 Debug: Lookup returned [object UIATableCell] with the name “Cedar 10 iPhone 4 iOS7” (id: 6).

[debug] [Instruments] [INST] 2017-02-03 15:55:33 +0000 Debug: responding with:
2017-02-03 15:55:33 +0000 Debug: Running system command #23: /Applications/Appium.app/Contents/Resources/node/bin/node /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/appium-ios-driver/node_modules/appium-uiauto/build/lib/bin/command-proxy-client.js /var/folders/56/cqxpk0p940582768bt7lvbqm0000gr/T/instruments_sock 2,{“status”:0,"v…

[debug] [UIAuto] Socket data received (38 bytes)

[debug] [UIAuto] Got result from instruments: {“status”:0,“value”:{“ELEMENT”:“6”}}
[MJSONWP] Responding to client with driver.findElement() result: {“ELEMENT”:“6”}
[HTTP] <-- POST /wd/hub/session/97362e4d-f97d-48b4-ae10-e7a923e4ea5b/element 200 1407 ms - 87
[HTTP] --> POST /wd/hub/session/97362e4d-f97d-48b4-ae10-e7a923e4ea5b/element/6/click {“sessionId”:“97362e4d-f97d-48b4-ae10-e7a923e4ea5b”,“id”:“6”}
[MJSONWP] Calling AppiumDriver.click() with args: [“6”,"97362e4d-f97d-48b4-ae…
[debug] [iOS] Executing iOS command ‘click’
[debug] [UIAuto] Sending command to instruments: au.tapById(‘6’)

[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 MobileGestaltHelper[83] : libMobileGestalt MobileGestalt.c:281: server_access_check denied access to question UniqueDeviceID for pid 192
[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 ScriptAgent[192] : libMobileGestalt MobileGestaltSupport.m:151: pid 192 (ScriptAgent) does not have sandbox access for re6Zb+zwFKJNlkQTUeT+/w and IS NOT appropriately entitled

[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 ScriptAgent[192] : libMobileGestalt MobileGestalt.c:542: no access to UniqueDeviceID (see rdar://problem/11744455)

[debug] [Instruments] [INST] 2017-02-03 15:55:34 +0000 Debug: Got new command 23 from instruments: au.tapById(‘6’)
[debug] [Instruments] [INST] 2017-02-03 15:55:34 +0000 Debug: evaluating au.tapById(‘6’)
2017-02-03 15:55:34 +0000 Debug: UIATableCell.tap()
[debug] [Instruments] [INST] 2017-02-03 15:55:34 +0000 Debug: UIATableCell could not be tapped
[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 MobileGestaltHelper[83] : libMobileGestalt MobileGestalt.c:281: server_access_check denied access to question UniqueDeviceID for pid 192
[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 ScriptAgent[192] : libMobileGestalt MobileGestaltSupport.m:151: pid 192 (ScriptAgent) does not have sandbox access for re6Zb+zwFKJNlkQTUeT+/w and IS NOT appropriately entitled
[iOSLog] [IOS_SYSLOG_ROW] Feb 3 15:55:34 Aspen-4-iPhone-4S-iOS8 ScriptAgent[192] : libMobileGestalt MobileGestalt.c:542: no access to UniqueDeviceID (see rdar://problem/11744455)

[debug] [Instruments] [INST] 2017-02-03 15:55:34 +0000 Error: VerboseError: elementId 6 could not be tapped

[debug] [UIAuto] Socket data received (57 bytes)

[debug] [UIAuto] Got result from instruments: {“status”:13,“value”:“elementId 6 could not be tapped”}
[HTTP] <-- POST /wd/hub/session/97362e4d-f97d-48b4-ae10-e7a923e4ea5b/element/6/click 500 1695 ms - 202

[HTTP] --> DELETE /wd/hub/session/97362e4d-f97d-48b4-ae10-e7a923e4ea5b {}
[MJSONWP] Calling AppiumDriver.deleteSession() with args: ["97362e4d-f97d-48b4-ae10-e…
[debug] [iOS] Deleting ios session
[debug] [UIAuto] Destroying instruments client socket.
[debug] [UIAuto] Closing socket server.
[debug] [UIAuto] Instruments socket server was closed
[debug] [Instruments] Starting shutdown.
[debug] [Instruments] Sending sigterm to instruments

[debug] [Instruments] [INST] 2017-02-03 15:55:34 +0000 Error: Error during eval: [native code]
file:///Applications/Appium.app/Contents/Resources/node_modules/BA62DC60-933C-483F-8F8C-6411D3F1DFC6/bootstrap-285ec024f36f1111.js:711:30
tapById@file:///Applications/Appium.app/Contents/Resources/node_modules/BA62DC60-933C-483F-8F8C-6411D3F1DFC6/bootstrap-285ec024f36f1111.js:1182:42
eval code

I ran into this issue before when running my iOS tests on Appium 1.5.3. I resolved it by tapping the element instead of using the click event.

Thanks for the tip, unfortunately it didn’t work for me.
Are you running now the appium 1.6 version? Could that be a solution?