GithubStar/appium
1
0
Fork 0
mirror of https://github.com/appium/appium.git synced 2026-10-29 04:36:39 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update troubleshooting.md

Browse Source 
Make people check if their keychain is unlocked.
[Link](https://github.com/appium/appium/issues/7705) to issue inspiring this change.
This commit is contained in:
h3dkandi
2017-01-19 09:52:48 +02:00
committed by GitHub
parent f5eb5fca2c
commit e7b75f33de
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/appium-setup/troubleshooting.md
+1
View File
@@ -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: