Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: troubleshooting.md #2020

Merged
merged 2 commits into from
Sep 23, 2023
Merged

docs: troubleshooting.md #2020

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
444addf
docs: troubleshooting.md
KazuCocoa Sep 23, 2023
21000a3
Update troubleshooting.md
KazuCocoa Sep 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ title: Troubleshooting

## Weird state

### stop responding
**Note:** Running `WebDriverAgent` tests on a real device is particularly flakey. If things stop responding, the only recourse is, most often, to restart the device. Logs in the form of the following _may_ start to occur:

```shell
Expand All @@ -24,6 +25,14 @@ dbug WebDriverAgent Device: Jul 26 13:21:57 iamPhone XCTRunner[240] <Warning>: E
dbug WebDriverAgent Device: Jul 26 13:22:57 iamPhone XCTRunner[240] <Warning>: Enqueue Failure: UI Testing Failure - App state of (null) is still unknown <unknown> 0 1
```

### Get a response after 60+ seconds after a session starts frequently

Did you experience an additional 60 seconds of slow command response that is usually should not take such a long time?
KazuCocoa marked this conversation as resolved.
Show resolved Hide resolved

`testmanagerd` could continue crashing against a target application. Then, WebDriverAgent gets an API result by XCTest framework after 60 seconds timeout. It could cause such a 60 seconds "hang" behavior.
KazuCocoa marked this conversation as resolved.
Show resolved Hide resolved
This can be fixed by terminating the target application process. For example, if this behavior occurs in `mobile: queryAppState` command call, you could terminate the application once, or restart the device entirely.
Then, such a slow behavior might be fixed after the process restart. Please check [WebDriverAgent#774](https://github.com/appium/WebDriverAgent/pull/774) as an example case.
KazuCocoa marked this conversation as resolved.
Show resolved Hide resolved

## Real device security settings

On some systems, especially CI ones, where tests are executed by a command line agents, macOS Accessibility restrictions make the `WebDriverAgent` system unable to retrieve the development keys from the system keychain. This is usually manifest
Expand Down
Loading