From e7b75f33deaa58c68c72941edf42ef153e733ff3 Mon Sep 17 00:00:00 2001 From: h3dkandi Date: Thu, 19 Jan 2017 09:52:48 +0200 Subject: [PATCH] Update troubleshooting.md Make people check if their keychain is unlocked. [Link](https://github.com/appium/appium/issues/7705) to issue inspiring this change. --- docs/en/appium-setup/troubleshooting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/en/appium-setup/troubleshooting.md b/docs/en/appium-setup/troubleshooting.md index 27fee5c46..fc1957e39 100644 --- a/docs/en/appium-setup/troubleshooting.md +++ b/docs/en/appium-setup/troubleshooting.md @@ -60,6 +60,7 @@ own items in the SDK manager. Make sure you install the build-tools and platform * If Instruments is crashing when running against a physical device ("exited with code 253"), ensure Xcode has downloaded device symbols. Go to Window -> Devices, and it should start automatically. This is needed after iOS version upgrades. * If you see `iOS Simulator failed to install the application.` and the paths are correct, try restarting the computer. +* Make sure your macOS keychain that holds the certificate(s) needed for building your app and the WebDriverAgent is unlocked. Especialy if you are using ssh. General symptom to look for is `codesign` failure. * If you have custom elements in your app, they will not be automatable by UIAutomation (and therefore Appium) by default. You need to set the accessibility status to 'enabled' on them. The way to do this in code is: